From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Moynihan Subject: Restricting the agenda to the current subtree Date: Fri, 23 Nov 2007 18:04:55 +0000 Message-ID: <47471647.8000308@calicojack.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ivctr-0001zj-04 for emacs-orgmode@gnu.org; Fri, 23 Nov 2007 13:05:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ivctq-0001yt-E4 for emacs-orgmode@gnu.org; Fri, 23 Nov 2007 13:05:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ivctq-0001yh-3f for emacs-orgmode@gnu.org; Fri, 23 Nov 2007 13:05:10 -0500 Received: from storm.bpweb.net ([83.223.106.8]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ivctp-0006Uq-8l for emacs-orgmode@gnu.org; Fri, 23 Nov 2007 13:05:09 -0500 Received: from [192.168.0.205] (host-77-97-226-21.static.telewest.net [77.97.226.21]) (authenticated bits=0) by storm.bpweb.net (8.13.1/8.13.1) with ESMTP id lANI530t010975 for ; Fri, 23 Nov 2007 18:05:08 GMT 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 I've just discovered that you can restrict the agenda view to the current subtree, and I think I'm going to find this very useful! Firstly is it possible to bind this to a simple key-chord though as I'm finding C-a < < a A little unwieldy. Also, how about implementing another "follow" command, that does the opposite of following movements in the agenda view and displaying them in the file. i.e. When enabled it uses the org-goto interface to follow movements within the file and display the restricted agenda view in another window. This could also be coupled with other queries defined in the agenda yet would narrow their focus to the currently browsed subtree. I'm not sure if it's a crazy idea or not but I think it might be useful. R.