emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: counter-intuitive key bindings
Date: Thu, 16 Aug 2007 08:13:02 +0200	[thread overview]
Message-ID: <1d7b76ad7d7a123048d2dc2f513f49aa@science.uva.nl> (raw)
In-Reply-To: <m2y7gcn3b0.fsf@cam.ac.uk>


On Aug 15, 2007, at 18:57, Leo wrote:

> On 2007-08-09 06:05 +0100, Carsten Dominik wrote:
>>> In this case, I feel there should a consistent definition of key
>>> bindings. One excellent example is vc, it is just so easy to 
>>> remember.
>>
>> What do you mean with "consistent definition of key bindings".
>>
>>> I have been an regular user of org, and I have already forgotten that
>>> S-up/down does priority change after one month's break.
>>
>> I have been trying very hard to make the key bindings as logical
>> as possible - but there is a huge amount of commands in org,
>> and many keys are needed.
>>
>> That said, the S-up/down for priorities does leas to a couple
>> of inconsistencies, in particular between agenda and org-mode buffers.
>>
>> - Carsten
>
> I know it is difficult to come up with good key bindings for so many
> commands that org-mode has. That's why I gave the example of vc, which
> has extremely excellent key bindings. I would never have to learn them 
> a
> second time. I hope someone can come up with something similar for org.

Well, this is not really a fair comparison, because vc has maybe 13
commands???  Sure, not too hard to make these stick in your head.

Obviously I have been trying to make the best key bindings I can.
Besides making them easy to remember you are of course limited
by Emacs conventions, and by the wish to avoid 3 keypress bindings for
speed.  And maybe some compromises because of the historical
development, to keep the habits of users.

I am certainly open for suggestions.

- Carsten


>
> -- 
> Leo <sdl.web AT gmail.com>                         (GPG Key: 9283AA3F)
>
>          Gnus is one component of the Emacs operating system.
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477

  reply	other threads:[~2007-08-16  7:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28 11:17 counter-intuitive key bindings Leo
2007-07-28 11:43 ` Bastien
2007-07-28 18:35   ` Leo
2007-08-09  5:05     ` Carsten Dominik
2007-08-15 16:57       ` Leo
2007-08-16  6:13         ` Carsten Dominik [this message]
2007-07-28 12:52 ` Adam Spiers
2007-08-10  6:57   ` Carsten Dominik
2007-09-01 10:22     ` Adam Spiers

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=1d7b76ad7d7a123048d2dc2f513f49aa@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=sdl.web@gmail.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
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).