From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Free `1' and `0' keys from the org-agenda interface ? Date: Tue, 16 Oct 2007 18:53:47 +0100 Message-ID: <87wstnkkt0.fsf@bzg.ath.cx> References: <87ejfvm0s3.fsf@bzg.ath.cx> <20071016163144.GE3018@atlantic.linksys.moosehall> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ihpfy-0001Oj-18 for emacs-orgmode@gnu.org; Tue, 16 Oct 2007 12:53:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ihpfv-0001OX-Rz for emacs-orgmode@gnu.org; Tue, 16 Oct 2007 12:53:48 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ihpfv-0001OU-Ot for emacs-orgmode@gnu.org; Tue, 16 Oct 2007 12:53:47 -0400 Received: from nf-out-0910.google.com ([64.233.182.185]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ihpfv-0007va-EU for emacs-orgmode@gnu.org; Tue, 16 Oct 2007 12:53:47 -0400 Received: by nf-out-0910.google.com with SMTP id f5so1780855nfh for ; Tue, 16 Oct 2007 09:53:46 -0700 (PDT) In-Reply-To: <20071016163144.GE3018@atlantic.linksys.moosehall> (Adam Spiers's message of "Tue, 16 Oct 2007 17:31:44 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Adam Spiers writes: > I'm curious about your suggestion of '<<' though - does that imply the > sub-keymap functionality I asked for already exists? I first thought yes, since it looks like the first `<' keystroke is waiting for the next one (at least from the description I proposed). But in fact there is no sub-keymap involved here: it's only about cycling through three states: - not-restricted - buffer-restricted - subtree/region-resctricted Then three keystrokes would turn off the restriction. But calling a sub-keymap with `<' could also be useful: `< <' : cycle through default restricted states (see above) `< f' : prompt for an org-agenda-file to restrict to `< s' : prompt for a subtree to restrict Caveat: we should better not allow interactive restriction to a property, since this is the job of the custom-command itself... My 2.5 cents. -- Bastien