emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: How you ORGanize yourself? (aka: Why not one file to rule'em all?)
Date: Tue, 20 Apr 2010 08:02:38 -0400	[thread overview]
Message-ID: <87k4s2z601.fsf@fastmail.fm> (raw)
In-Reply-To: <56459EC5-E302-472B-BFEF-A8FFA1CB6FD4@gmail.com> (Carsten Dominik's message of "Mon, 19 Apr 2010 18:08:52 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On Apr 19, 2010, at 5:07 PM, Matthew Lundin wrote:
>
>> I find that (org-agenda-restriction-lock) makes subsequent calls to
>> my-org-agenda-files-by-filetag slow, since it refreshes the current
>> agenda.
>>
>>
>> Are there any potential pitfalls if I use (setq org-agenda-restrict
>> nil)
>> instead?
>
> I think you might mean org-agenda-remove-restriction-lock?

Yes, sorry for the typo.

> That function does some cleanup which I think you should keep,
> so maybe just call it like this:
>
> (org-agenda-remove-restriction-lock 'noupdate)

Thanks! This was exactly what I was looking for.

> Otherwise, while you are inside your system, (setq org-agenda-restrict
> nil) is enough - only when you mix the normal subtree/file restriction
> with you system, you may get funny effects.

I've put updated versions of the functions on Worg:

http://orgmode.org/worg/org-hacks.php#set-agenda-files-by-filetag

Best,
Matt

  reply	other threads:[~2010-04-20 11:57 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
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 [this message]
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=87k4s2z601.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=carsten.dominik@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).