From: Carsten Dominik <carsten.dominik@gmail.com>
To: Benjamin Andresen <bandresen@gmail.com>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Re: POLL: Change of keys to move agenda through time
Date: Tue, 25 Aug 2009 13:48:13 +0200 [thread overview]
Message-ID: <BC1379D9-BD13-4D5A-92C7-471E170FF204@gmail.com> (raw)
In-Reply-To: <87ocq4xgxd.fsf@gmail.com>
Hi everyone,
I tend to agree with the arguments that "n" and "p" should move
vertically in the agenda buffer, because many Emacs modes do
it like this.
So it seem to me that this discussion should focus on which keys should
move the agenda forward and backward in time.
- Carsten
On Aug 25, 2009, at 1:37 PM, Benjamin Andresen wrote:
> Hey Bastien,
>
> Bastien <bastienguerry@googlemail.com> writes:
>
>> Benjamin Andresen <bandresen@gmail.com> writes:
>>> But "n" and "p" are already used to move up and down entries in the
>>> org-agenda.
>>> Where would they go to then?
>>
>> C-n and C-p, like in any Emacs buffer?
>
> Sure. That's a given. But they seem to be the fallback, IMO.
>
> As Leo wrote: ibuffer, gnus, dired & others all use 'n' for next
> line and 'p' for previous line.
>
> And with the recent mark and unmark feature inspired by dired, doing
> what it does, seems intuitive as far as emacs goes.
>
> Another example I can think of:
> epa-list-keys uses 'n' and 'p' and 'm' and 'u' for the same things
> as dired and ibuffer.
>
> Basically it's the Principle Of Least Surprise. "n", "p" doing what it
> does now falls under it for me, based on all the other software I use.
>
> br,
> benny
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-08-25 11:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 9:12 POLL: Change of keys to move agenda through time Carsten Dominik
2009-08-24 17:14 ` Bastien
2009-08-25 9:26 ` Benjamin Andresen
2009-08-24 17:15 ` Bastien
2009-08-25 11:37 ` Benjamin Andresen
2009-08-24 20:59 ` Bastien
2009-08-25 11:48 ` Carsten Dominik [this message]
2009-08-25 12:20 ` Chris Leyon
2009-08-24 21:00 ` Bastien
2009-08-25 12:23 ` Carsten Dominik
2009-08-25 14:11 ` Bernt Hansen
2009-08-25 15:10 ` Sébastien Vauban
2009-08-25 12:20 ` Manuel Hermenegildo
2009-08-25 10:59 ` Leo
2009-08-25 12:09 ` Leo
2009-08-25 11:05 ` Niels Felsted Thorsen
2009-08-25 11:20 ` Manish
2009-08-25 11:35 ` Michaël Parienti
2009-08-25 11:42 ` Charles Philip Chan
2009-08-25 11:55 ` Noorul Islam
2009-08-25 12:05 ` Manuel Hermenegildo
2009-08-25 13:07 ` Michael Gilbert
2009-08-25 13:13 ` Matt Lundin
2009-08-25 14:53 ` Jonathan Arkell
2009-08-25 15:08 ` Christian Egli
2009-08-25 15:31 ` Manish
2009-08-25 15:39 ` Chris Leyon
2009-08-26 4:44 ` Carsten Dominik
2009-08-25 16:02 ` Carsten Dominik
2009-08-25 15:13 ` Rainer Stengele
2009-08-27 3:19 ` Daniel Martins
2009-08-25 15:30 ` OrgmodePOLL: " Wes Hardaker
2009-08-25 21:27 ` OrgmodeOrgmodePOLL: " Wes Hardaker
2009-08-25 21:38 ` Dale Smith
2009-08-26 2:39 ` POLL: " Memnon Anon
2009-08-26 3:27 ` Samuel Wales
2009-08-26 3:37 ` Samuel Wales
2009-08-26 6:08 ` Jean-Marie Gaillourdet
2009-08-26 9:06 ` Carsten Dominik
2009-08-26 6:22 ` Bastien
2009-08-27 14:12 ` Carsten Dominik
2009-08-27 1:05 ` Samuel Wales
2009-08-27 9:53 ` Carsten Dominik
2009-08-27 4:05 ` Gregory J. Grubbs
2009-08-27 4:47 ` Charles Philip Chan
2009-08-27 7:17 ` Peter Frings
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC1379D9-BD13-4D5A-92C7-471E170FF204@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bandresen@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.