From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Lundin Subject: Re: Re: How you ORGanize yourself? (aka: Why not one file to rule'em all?) Date: Mon, 19 Apr 2010 11:07:22 -0400 Message-ID: <87r5mbpjkl.fsf@fastmail.fm> References: <87k4s6ur0i.fsf@fastmail.fm> 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 1O3sXT-0001aI-70 for emacs-orgmode@gnu.org; Mon, 19 Apr 2010 11:05:31 -0400 Received: from [140.186.70.92] (port=46119 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3sXR-0001a0-Kz for emacs-orgmode@gnu.org; Mon, 19 Apr 2010 11:05:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3sXO-0001Vb-NI for emacs-orgmode@gnu.org; Mon, 19 Apr 2010 11:05:29 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:53413) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3sXO-0001VK-Kz for emacs-orgmode@gnu.org; Mon, 19 Apr 2010 11:05:26 -0400 In-Reply-To: (Carsten Dominik's message of "Sat, 17 Apr 2010 22:54:33 +0200") 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: Carsten Dominik Cc: Org Mode Hi Carsten, Carsten Dominik writes: > On Apr 17, 2010, at 3:50 PM, Matt Lundin wrote: > >> FWIW, I've found it quite convenient to rely on filetags to organize >> my notes. I've written a few functions that allow me to limit my >> agenda to a subset of agenda files that share a filetag (e.g., >> "emacs" or "writing"). This is a bit quicker than calling agenda >> commands on all agenda files and then filtering afterward. It also >> allows for greater focus on a particular area of work. Here are the >> functions: >> http://orgmode.org/worg/org-hacks.php#set-agenda-files-by-filetag > > > Hi Matt, > > this is very interesting! > > One idea: Instead of setting the value of org-agenda-files, > you can also restrict in the following way: > > (org-agenda-remove-restriction-lock) > (put 'org-agenda-files 'org-restrict my-file-list) > (setq org-agenda-overriding-restriction 'files) > > The restriction sticks until you remove it with `C-c C_x >' > > I am not sure this will work better for your case - but maybe it will. Thanks for the tip! That's much more elegant. I find that (org-agenda-restriction-lock) makes subsequent calls to my-org-agenda-files-by-filetag slow, since it refreshes the current agenda. Are there any potential pitfalls if I use (setq org-agenda-restrict nil) instead? Thanks, Matt