emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: How you ORGanize yourself? (aka: Why not one file to rule'em all?)
Date: Sat, 17 Apr 2010 09:50:53 -0400	[thread overview]
Message-ID: <87k4s6ur0i.fsf@fastmail.fm> (raw)
In-Reply-To: <i2z1e5bcefd1004142241hf113012webd11a57afea4319@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Thu, 15 Apr 2010 00:41:19 -0500")

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

Best,
Matt

  parent reply	other threads:[~2010-04-17 13:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15  5:41 How you ORGanize yourself? (aka: Why not one file to rule'em all?) Marcelo de Moraes Serpa
2010-04-16 12:43 ` tycho garen
2010-04-17 13:50 ` Matt Lundin [this message]
2010-04-17 20:54   ` Carsten Dominik
2010-04-18  6:35     ` Marcelo de Moraes Serpa
2010-04-18  6:51       ` Marcelo de Moraes Serpa
2010-04-19 15:07     ` Matthew Lundin
2010-04-19 16:08       ` Carsten Dominik
2010-04-20 12:02         ` Matthew Lundin
2010-04-20 19:59 ` Flavio Souza
2010-04-20 23:16   ` Greg Newman
2010-04-21  9:51     ` Alan E. Davis
2010-04-21 11:38       ` Tim O'Callaghan
2010-04-21 12:52       ` Bernt Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k4s6ur0i.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).