From: Chris Leyon <cleyon@gmail.com>
To: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Re: POLL: Change of keys to move agenda through time
Date: Tue, 25 Aug 2009 08:20:53 -0400 [thread overview]
Message-ID: <5ea706d0908250520u62ca057cq138201f1397b2c4b@mail.gmail.com> (raw)
In-Reply-To: <BC1379D9-BD13-4D5A-92C7-471E170FF204@gmail.com>
Another solution would be to use "f" and "b" to move forward and
backward in time. Some other Agenda bindings would have to change to
accommodate this. Old "f" (org-agenda-follow-mode) could become "F"
which is unused. But "b" and "B" are both used and would need to be
remapped.
Obviously this is not the easiest possible solution. However, these
bindings would be very consistent with the conventions of most other
Emacs packages.
The agenda mode bindings are getting very crowded with many functions
and free keys are running out. It may be time to start creating
prefix-keys/dispatchers a la Dired and Gnus.
On Tue, Aug 25, 2009 at 07:48, Carsten Dominik<carsten.dominik@gmail.com> wrote:
> 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.
next prev parent reply other threads:[~2009-08-25 12:20 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
2009-08-25 12:20 ` Chris Leyon [this message]
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
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=5ea706d0908250520u62ca057cq138201f1397b2c4b@mail.gmail.com \
--to=cleyon@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 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).