From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Darlan Cavalcante Moreira <darcamo@gmail.com>
Cc: emacs-orgmode@gnu.org, Brian Wood <bwood@berkeley.edu>,
Joseph Kern <jkern@semafour.net>
Subject: Re: Best practices? Multiple .org files?
Date: Fri, 2 Sep 2011 00:47:07 +0200 [thread overview]
Message-ID: <CAMXnza3ZEM7cuWWNedz756jxvpid0ZSREeh7KNWFGOFm4UNH4g@mail.gmail.com> (raw)
In-Reply-To: <4e5ff2b5.8273ec0a.6ded.2521@mx.google.com>
On Thu, Sep 1, 2011 at 11:01 PM, Darlan Cavalcante Moreira
<darcamo@gmail.com> wrote:
> But the original question remains. Is it better, regarding speed, to split
> the content into several files (all included in the agenda) or a single
> file will be faster?
>
If you have source blocks, one big file might be slow. As far as I
recall the issue was font-lock. I personally go for several agenda
files in the root directory categorised depending on kind of tasks or
notes. I have subdirectories (not included in agenda files) for
details on various projects. These are included in the
org-agenda-text-search-extra-files, so they are included when I do C-c
a s.
I hope that helps.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-09-01 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 17:35 Best practices? Multiple .org files? Brian Wood
2011-09-01 17:55 ` Joseph Kern
2011-09-01 18:38 ` Brian Wood
2011-09-01 21:01 ` Darlan Cavalcante Moreira
2011-09-01 22:47 ` suvayu ali [this message]
2011-09-02 10:35 ` Christian Moe
2011-09-02 12:37 ` Joseph Kern
2011-09-02 12:55 ` Eric S Fraga
2011-09-02 16:36 ` Brian Wood
2011-09-02 18:28 ` Eric S Fraga
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=CAMXnza3ZEM7cuWWNedz756jxvpid0ZSREeh7KNWFGOFm4UNH4g@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=bwood@berkeley.edu \
--cc=darcamo@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkern@semafour.net \
/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).