From: Carsten Dominik <carsten.dominik@gmail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] New variable to speed up custom agendas
Date: Thu, 11 Mar 2010 11:33:38 +0100 [thread overview]
Message-ID: <3620D2E1-454E-495A-AA05-CC43EF94B27E@gmail.com> (raw)
In-Reply-To: <87r5nrcx9a.fsf@fastmail.fm>
Hi Matt,
sorry, it looks like I forgot to push yesterday evening. Done now...
- Carsten
On Mar 11, 2010, at 5:12 AM, Matthew Lundin wrote:
> Hi Carsten,
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> wow, you have proven me wrong. There is a way to get
>> a significant speedup in agenda construction, for special
>> cases like you mentioned in an earlier message. This is
>> brilliant.
>>
>> I have taken the patch, with a few small modifications:
>>
>> 1. I changed the constant `org-agenda-custom-commands-local-options'
>> so that it will become a lot easier to bind this variable as an
>> an option when configuring `org-agenda-custom-commands' using
>> the customize interface.
>>
>> 2. I modified the docstring of the new variable so that the first
>> line
>> is a stand-alone sentence, as required in Emacs.
>>
>> 3. I moved the description of the symbols into your new variable,
>> and made org-diary point to it. I think the new location is
>> a better place for this.
>
> Thanks for applying the patch and for making these additional
> modifications!
>
>> Excellent, thank you very much. Will you add an example to
>> your org-agenda-custom-commands tutorial?
>
> I would be glad to. I'll put it on my todo list. :)
>
> - Matt
>
- Carsten
prev parent reply other threads:[~2010-03-11 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 4:39 [PATCH] New variable to speed up custom agendas Matt Lundin
2010-03-10 16:15 ` Carsten Dominik
2010-03-11 4:12 ` Matthew Lundin
2010-03-11 10:33 ` Carsten Dominik [this message]
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=3620D2E1-454E-495A-AA05-CC43EF94B27E@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).