From: Peter Frings <peter.frings@agfa.com>
To: emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Problem with shift-up
Date: Fri, 19 Aug 2011 17:10:48 +0200 [thread overview]
Message-ID: <C0C73985-F92D-4807-B31B-3D419AFE15E0@agfa.com> (raw)
Hi gang,
sorry to bother you all again, but my transition to the new emacs is now taking days and I’m getting really frustrated.
I’m trying to find out why shift-arrow on a date/time stamp no longer works with my brand new and shiny set-up.
Emacs 23, org-mode 7.7.
When running a minimal set-up (as described on the worg-FAQ), the shift-arrows keys work as expected: they change the date and time values in org’s timestamps.
When loading the starter-kit from Kieran Healy [1], things are not so smooth. I’ve been disabling all possible packages, trying to isolate the culprit, but to no avail. I searched the web and this mailing list, and found someone else with the same problem [2], but alas, no conclusive answer.
In both cases, 'shift-select-mode’ is t.
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’.
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? How can I find the guilty one so I can do very cruel things to it?
Pointers very much appreciated!
Peter.
[1] http://kjhealy.github.com/emacs-starter-kit/
[2] http://comments.gmane.org/gmane.emacs.orgmode/34329
next reply other threads:[~2011-08-19 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 15:10 Peter Frings [this message]
2011-08-19 20:10 ` Problem with shift-up Bastien
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=C0C73985-F92D-4807-B31B-3D419AFE15E0@agfa.com \
--to=peter.frings@agfa.com \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).