From: Shelagh Manton <shelagh.manton@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Having (too) many files in org-agenda-files
Date: Wed, 29 Sep 2010 13:39:00 +1000 [thread overview]
Message-ID: <87fwwtte0b.fsf@gmail.com> (raw)
In-Reply-To: 878w2lso50.fsf@mundaneum.com
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com>
writes:
> Hi,
>
> Of course, I have many, many files in Org mode. All files I write (or touch)
> in fact.
>
> Of course, I would like to search through my files at some point in time.
> I even would like to search through your files at some point in time, I mean
> through =org-mode/contrib/babel= and =Worg= for example.
[snip]
>
> You'll tell me: not a problem, you do that only once a day, and you use Emacs
> client/server for the rest of the time. True. A bit, because I sometimes have
> to restart Emacs for testing a fresh one (not impacted by defvars already
> defined, or deffaces, etc.).
>
> Having to wait almost 4 minutes is a real pain. So, here my
> comments/questions:
>
> - Isn't it possible to delay the fontification/ispell/etc. to when we really
> display (i.e., pop up) the buffer? I guess this must be a major component
> of the time this takes.
>
> - Couldn't we have 2 vars: =org-agenda-files= for the files you know you want
> have scanned for the agenda construction, and an extra list such as
> =org-search-files= for files not containing any dates? Then, some time
> would have to be taken when =C-c a s=, but not before. And not if you don't
> search for anything in your Org files during that Emacs session...
>
> Any other idea?
I use the jit-lock package that comes with emacs. "Stealth fontifying"
It makes font-lock only happen after the buffer is loaded and when you
are not doing anything else. You can access the variables through
customize-group RET jit-lock. It may be helpful here.
Shelagh
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-09-29 3:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 18:45 Having (too) many files in org-agenda-files Sébastien Vauban
2010-09-28 20:19 ` Matt Lundin
2010-09-29 21:21 ` Sébastien Vauban
2010-09-29 3:39 ` Shelagh Manton [this message]
2010-09-29 8:52 ` Sébastien Vauban
2010-09-29 3:56 ` Carsten Dominik
2010-09-29 8:32 ` Sébastien Vauban
2010-09-29 13:19 ` Carsten Dominik
2010-09-29 22:20 ` Sébastien Vauban
2010-09-30 11:24 ` Carsten Dominik
2010-09-30 11:53 ` Sébastien Vauban
2010-09-30 15:33 ` Nick Dokos
2010-09-30 17:08 ` Sébastien Vauban
2010-09-30 17:37 ` Carsten Dominik
2010-12-01 19:46 ` Sébastien Vauban
2010-12-01 23:00 ` Eric S Fraga
[not found] ` <17540.1291246717@gamaville.americas.hpqcorp.net>
2010-12-02 8:57 ` Eric S Fraga
2010-12-02 9:25 ` Sébastien Vauban
2010-12-12 18:28 ` David Maus
2010-12-02 3:10 ` Jeff Horn
2010-12-02 9:15 ` Sébastien Vauban
2010-10-06 14:47 ` Daniel Clemente
2010-09-30 13:37 ` Sébastien Vauban
2010-09-30 13:41 ` Carsten Dominik
2010-09-29 12:38 ` Matt Lundin
2010-09-29 12:47 ` Matthew Lundin
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=87fwwtte0b.fsf@gmail.com \
--to=shelagh.manton@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).