Re: Re: How you ORGanize yourself? (aka: Why not one file to rule'em all?)

[Carsten Dominik <carsten.dominik@gmail.com>]

On Apr 19, 2010, at 5:07 PM, Matthew Lundin wrote:

> Hi Carsten,
>
> Carsten Dominik <carsten.dominik@gmail.com> 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?


I think you might mean org-agenda-remove-restriction-lock?

That function does some cleanup which I think you should keep,
so maybe just call it like this:

(org-agenda-remove-restriction-lock 'noupdate)

Otherwise, while you are inside your system, (setq org-agenda-restrict  
nil)
is enough - only when you mix the normal subtree/file restriction with
you system, you may get funny effects.

- Carsten