emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: Free `1' and `0' keys from the org-agenda interface ?
Date: Wed, 17 Oct 2007 18:03:03 +0100	[thread overview]
Message-ID: <20071017170303.GC10874@atlantic.linksys.moosehall> (raw)
In-Reply-To: <bb09e941e67074c62de1858bbae9c764@science.uva.nl>

On Wed, Oct 17, 2007 at 05:47:58PM +0200, Carsten Dominik wrote:
> On Oct 16, 2007, at 23:26, Bastien wrote:
> >Adam Spiers <orgmode@adamspiers.org> writes:
> >
> >>>`< <' : cycle through default restricted states (see above)
> >>
> >>Hmm, that doubles the number of keypresses to achieve a given state,
> >>which is a bit cumbersome.  But if it's customizable, who cares? :-)
> >
> >I wouldn't mind having single keys to achieve this - it's just that I
> >thought `1' and `0' where not the best choice.
> 
> Yes, I can see that the 0 and one would be useful in other 
> circumstances.
> And I don't *relly* think that a double "<" would be so bad, because
> don't think restricting an agenda command to a region or subtree is
> used frequently, is it?

I have recently started using it quite a lot, e.g. to narrow to my
work or personal TODOs, which are both in files of their own.

But if sub-keymaps were to be implemented, this would be customizable
anyway, so we wouldn't need to worry about it.

  reply	other threads:[~2007-10-17 17:03 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
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 [this message]
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=20071017170303.GC10874@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).