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

[Marcelo de Moraes Serpa <celoserpa@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2678 bytes --]

Actually, what I want is to show the path to the item, it arealdy does it
when I have the item on focus, but maybe an option to display it on the todo
list would be nice :)

On Sun, Apr 18, 2010 at 1:35 AM, Marcelo de Moraes Serpa <
celoserpa@gmail.com> wrote:

> Thank you for the replies ;)
>
> One thing that I miss, is a way to make org-todo-list where each todo item
> would, somehow, show its parent until the topmost (or with configurable
> levels). Is it possible somehow? It would make it more easier to keep
> projects in only one file (GTD.org for example). I can use follow mode, but
> this would be nice.
>
> Thanks,
>
> Marcelo.
>
>
> On Sat, Apr 17, 2010 at 3:54 PM, Carsten Dominik <
> carsten.dominik@gmail.com> wrote:
>
>>
>> On Apr 17, 2010, at 3:50 PM, Matt Lundin wrote:
>>
>>  Hi Marcelo,
>>>
>>> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>>>
>>>  This is a thread to share your org dir (you have one right) file
>>>> structure. The title is because I see many of org users prefer having
>>>> big monolithic files, and I have a slightly different line of thought.
>>>>
>>>
>>> I have a handful of central files: e.g, inbox.org, reading.org,
>>> computer.org, writing.org, and so on. I've found, however, that on my
>>> relatively modest machines org/outline buffers slow down at appr.
>>> 12,000+ lines and become more or less unnavigable at appr. 30,000+ lines
>>> (especially if they have a deeply nested structure). Whenever a file
>>> gets too large, I simply create new files for sub-projects and
>>> sub-topics (e.g., perl.org, emacs.org, etc.) and link to them from the
>>> main file (e.g., computer.org). I also do a lot of archiving.
>>>
>>> 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.
>>
>> - Carsten
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 4259 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode