From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: Free `1' and `0' keys from the org-agenda interface ?
Date: Tue, 16 Oct 2007 17:31:44 +0100 [thread overview]
Message-ID: <20071016163144.GE3018@atlantic.linksys.moosehall> (raw)
In-Reply-To: <87ejfvm0s3.fsf@bzg.ath.cx>
Bastien (bzg@altern.org) wrote:
> Hi all,
>
> i'd like to have your opinion on this.
>
> I tend to use my `org-agenda-custom-commands' in a strict order.
> I first check for a first view, then check for a second view, etc.
> It would be nice to be able to use `1' for the first view -- but
> it's currently used to restrict the agenda view to the buffer.
>
> My suggestion for a possible replacement for the `1' and `0' keys
> would be this:
>
> `<' : restrict to the buffer
> `<<' : restrict to the region or subtree
>
> Note: `<' could also be `@' since `C-c @' means select the current
> subtree.
>
> I think it's okay to have some kind of "incremental" restriction,
> but I'm not sure about this. And I'd definitely like to have the
> [0-9] keys for my own agenda views :)
Wow, what can I say? I think those two mails arrived with 30 seconds
of each other - great minds think alike ;-)
I'm only just starting to use custom commands; however, your comment
about typically invoking custom commands in a strict order doesn't
surprise me. I might well find my usage habits following the same
trait.
I'm curious about your suggestion of '<<' though - does that imply the
sub-keymap functionality I asked for already exists?
next prev parent reply other threads:[~2007-10-16 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 17:23 Free `1' and `0' keys from the org-agenda interface ? Bastien
2007-10-16 16:31 ` Adam Spiers [this message]
2007-10-16 17:53 ` Bastien
2007-10-16 17:39 ` Adam Spiers
2007-10-16 21:26 ` Bastien
2007-10-17 15:47 ` Carsten Dominik
2007-10-17 17:03 ` Adam Spiers
2007-10-16 23:49 ` Andrew J. Korty
2007-10-17 1:13 ` Bastien
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=20071016163144.GE3018@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.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).