From: Carsten Dominik <email@example.com>
To: Paolo Petta <firstname.lastname@example.org>
Subject: Re: Minor request: full support of "ESC" as Meta key
Date: Wed, 27 May 2009 21:18:56 +0200 [thread overview]
Message-ID: <5002669B-85ED-4E82-B792-7ECE06BEFBDB@gmail.com> (raw)
I have applied your patch, only moving some of the bindings into the
On May 26, 2009, at 7:50 PM, Paolo Petta wrote:
> Dear Carsten -
> many thanks for following up on this (and to the list for bearing
> with me!) --- more in a direct/private email.
> On Tue, 26 May 2009, Carsten Dominik wrote:
>> Date: Tue, 26 May 2009 19:25:01 +0200
>> From: Carsten Dominik <email@example.com>
>> To: Paolo Petta <firstname.lastname@example.org>
>> Cc: email@example.com
>> Subject: Re: [Orgmode] Minor request: full support of "ESC" as Meta
>> Hi Paolo,
>> normally, meta key bindings should automatically also affect ESC
>> bindings. So it should not be necessary, even though I see that I
>> have done this in some cases, very like upon requests like your's.
>> If you try to come up with a list of affected bindings/commands, I
>> will add these specific bindings. However, as you have noticed,
>> some keys in orgstruct-mode may be difficult.
>> - Carsten
>> On May 24, 2009, at 2:15 AM, Paolo Petta wrote:
>>> [Dear moderator:
>>> this is of course a minor remark, and it is clearly not up to me to
>>> decide whether it is worth while being recorded at all, let alone
>>> being spread to the mailing list!
>>> But I still do hope it is not considered a downright abuse of your
>>> I only just started to look into Org: As "OS-hopper" using emacs
>>> regularly on different versions of Linux, Windows, and Mac OS, the
>>> comprehensive cross-platform support that Org promises is highly
>>> But trying to use Org relying on the Escape key as 'Meta', I
>>> discovered that Org's support in this regard is currently spotty.
>>> While for some key combinations both the [?\e (...)] and the
>>> [(meta ...)] variants are defined, it is only the [(meta ...)]
>>> definitions that are fully covered. For example, org-insert-todo-
>>> heading - one of the very first org-specific key-combinations
>>> introduced in the very useful Org tutorial - is mapped only to
>>> [(meta shift return)], the "ESC-based" equivalent [?\e (shift
>>> return)] is missing (org.el, line 13905).
>>> While I've tried to patch up org.el the best I could with the
>>> missing keymap definitions (and so far I have not run into
>>> problems), I am not proficient enough an elisp programmer to dare
>>> provide my fixes: e.g. I'm not at all sure to have made the
>>> correct additions to the section introduced with the comment
>>> ";; Special treatment needed for TAB and RET" on line 6836 of
>>> the specification of disputed keys on line 331ff in org.el would
>>> be another example.
>>> I would therefore like to ask to please consider putting 'full'
>>> coverage for both keymap variants on the todo list for an upcoming
>>> With many thanks in advance!
>>> Paolo Petta
>>> Austrian Research Inst. for Artificial Intelligence
>>> Freyung 6/6, A 1010 Vienna, Austria, Europe Paolo.Petta <@>
>>> Emacs-orgmode mailing list
>>> Remember: use `Reply All' to send replies to the list.
> Paolo Petta
> Austrian Research Inst. for Artificial Intelligence
> Freyung 6/6, A 1010 Vienna, Austria, Europe Paolo.Petta <@>
prev parent reply other threads:[~2009-05-27 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 0:15 Minor request: full support of "ESC" as Meta key Paolo Petta
2009-05-26 17:25 ` Carsten Dominik
2009-05-26 17:50 ` Paolo Petta
2009-05-27 19:18 ` Carsten Dominik [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).