From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo de Moraes Serpa Subject: Re: Re: How you ORGanize yourself? (aka: Why not one file to rule'em all?) Date: Sun, 18 Apr 2010 01:35:39 -0500 Message-ID: References: <87k4s6ur0i.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1463535490==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3O6l-0002YN-0X for emacs-orgmode@gnu.org; Sun, 18 Apr 2010 02:35:55 -0400 Received: from [140.186.70.92] (port=53345 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3O6g-0002Y1-Kk for emacs-orgmode@gnu.org; Sun, 18 Apr 2010 02:35:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3O6Z-0003fZ-Ai for emacs-orgmode@gnu.org; Sun, 18 Apr 2010 02:35:50 -0400 Received: from mail-iw0-f176.google.com ([209.85.223.176]:56970) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3O6Y-0003ex-Oz for emacs-orgmode@gnu.org; Sun, 18 Apr 2010 02:35:42 -0400 Received: by iwn6 with SMTP id 6so2393030iwn.26 for ; Sat, 17 Apr 2010 23:35:41 -0700 (PDT) In-Reply-To: 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: Matt Lundin , Org Mode --===============1463535490== Content-Type: multipart/alternative; boundary=0016363b9124844a7604847d0d02 --0016363b9124844a7604847d0d02 Content-Type: text/plain; charset=ISO-8859-1 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 wrote: > > On Apr 17, 2010, at 3:50 PM, Matt Lundin wrote: > > Hi Marcelo, >> >> Marcelo de Moraes Serpa 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 > > --0016363b9124844a7604847d0d02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 t= he 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 1= 7, 2010 at 3:54 PM, Carsten Dominik <carsten.dominik@gmail.com> wrote:=
<= div class=3D"h5">
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: =A0Instead 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.
<= font color=3D"#888888">
- Carsten


--0016363b9124844a7604847d0d02-- --===============1463535490== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============1463535490==--