From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: FR: more flexible customization of org-agenda-custom-commands key bindings
Date: Tue, 30 Oct 2007 07:06:03 +0100 [thread overview]
Message-ID: <FB56D07B-28E6-4906-B81A-1E6EB80E07C8@science.uva.nl> (raw)
In-Reply-To: <87ir4r2tdt.fsf@bzg.ath.cx>
On 28Oct2007, at 3:42 PM, Bastien wrote:
> Adam Spiers <orgmode@adamspiers.org> writes:
>
>>> If the idea is just to re-display the *Org agenda* buffer
>>
>> Correct. It's effectively a more generic version of "Press `C-u
>> r' to
>> search again with new search string".
>
> So why not just make `C-u r' call the *agenda commands* buffer back
> when
> the current agenda view is produced by (org-agenda-list)?
>
> Then `C-u r' will have the same meaning across all possible types of
> agenda views, i.e. call `org-agenda-redo' and wait for more
> information
> on how to refine the current view. Which means: call back `org-
> agenda'
> if the last command was `org-agenda-list'.
This is not possible, because the prefix argument is needed to be
passed to the
command that is executed by the "r" command.
>
> I think it will be hard to have a simpler keystroke than `C-x b' :)
> But anyway, I guess your point is to have some Org internal command
> for
> this function -- which would also avoid the problem with ido.el.
We could use "e" for "execute agenda command"?
>
>> I can't think of a good mnemonic for binding any of these to this
>> operation. My preferred solution would be the following, though I
>> would understand if it was rejected on the grounds of being too
>> disruptive to what users are used to:
>>
>> - rebind 'r' to this operation, since 'redo' or 'repeat' is the
>> most
>> obvious mnemonic,
>>
>> - rebind 'g' to `org-agenda-redo', since 'g' is a universal emacs
>> keybinding meaning 'refresh the current buffer display', and
>>
>> - bind 'G' to `org-agenda-toggle-time-grid', since this is a less
>> frequent operation and hence can be moved to the chord "shift-G"
>> without causing hassle.
I do agree with the last two, "g" should indeed be the refresh command.
However, I'm hesitating to change the "r" binding, I believe that
many people
(including me) are too used to this key binding.
- Carsten
next prev parent reply other threads:[~2007-10-30 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 16:20 FR: more flexible customization of org-agenda-custom-commands key bindings Adam Spiers
2007-10-16 16:36 ` Adam Spiers
2007-10-18 5:35 ` Carsten Dominik
2007-10-18 9:59 ` Bastien
2007-10-27 13:40 ` Adam Spiers
2007-10-28 14:42 ` Bastien
2007-10-30 6:06 ` Carsten Dominik [this message]
2007-10-30 8:53 ` Adam Spiers
2007-10-30 18:18 ` Bastien
2007-10-16 17:38 ` Bastien
2007-10-17 13:03 ` Bastien
2007-10-17 14:04 ` Adam Spiers
2007-10-17 22:06 ` Carsten Dominik
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=FB56D07B-28E6-4906-B81A-1E6EB80E07C8@science.uva.nl \
--to=carsten.dominik@gmail.com \
--cc=bzg@altern.org \
--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).