emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: Peter Frings <peter.frings@agfa.com>
Cc: emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Problem with shift-up
Date: Fri, 19 Aug 2011 22:10:45 +0200	[thread overview]
Message-ID: <871uwhduwq.fsf@gnu.org> (raw)
In-Reply-To: <C0C73985-F92D-4807-B31B-3D419AFE15E0@agfa.com> (Peter Frings's message of "Fri, 19 Aug 2011 17:10:48 +0200")

Hi Peter,

Peter Frings <peter.frings@agfa.com> writes:

> When loading the starter-kit from Kieran Healy [1], 

AFAIU, this starter-kit relies on the commit c88c76b of Org:
https://github.com/kjhealy/emacs-starter-kit/tree/master/src

Please make sure to report what your exact version of Org is (M-x
org-version), that might help.

> In both cases, 'shift-select-mode’ is t.

What is the value of `org-support-shift-select'?  Maybe the 
starter-kit is setting this variable.

> With the minimal set-up,  S-up is bound to this (using C-h k):
> <S-up> runs the command org-shiftup, which is an interactive compiled
> Lisp function in `org.el’.

Good :)

> With the starter-kit, it’s:
> <up> (translated from <S-up>) runs the command previous-line, which is
> an interactive compiled Lisp function in `simple.el’.
>
> What the heck is ‘translating’ this key binding? 

When a composed keybinding like <S-up> does not point to any command,
Emacs "translates" it to <up> and use the associated command instead.

> How can I find the guilty one so I can do very cruel things to it?

I suggest you ask to the author of the starter-kit :)

Let us know if you make progress,

-- 
 Bastien

next prev parent reply	other threads:[~2011-08-19 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 15:10 Problem with shift-up Peter Frings
2011-08-19 20:10 ` Bastien [this message]
2011-08-19 20:37 ` Ista Zahn
2011-08-22  8:09   ` peter.frings
2011-08-22 15:57     ` Problem with shift-up [solved] Peter Frings
2011-08-23 16:24       ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871uwhduwq.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=peter.frings@agfa.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).