From: Carsten Dominik <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: Agenda optimization (new worg page and new defaults)
Date: Wed, 6 Mar 2013 11:02:47 +0100 [thread overview]
Message-ID: <4C79050C-3F27-427D-98F0-8DA6D6B074CA@gmail.com> (raw)
I think this is the right decision, thanks. And thanks for the nice documentation! Tis might deserve a spot in the manual, in the final chapter.....
On 6 mrt. 2013, at 10:45, Bastien <firstname.lastname@example.org> wrote:
> Hi all,
> I wrote a worg page with some advice on how to speed up agenda
> I also reverted the change for two variables:
> Those used to be respectively nil and t, and while working on
> agenda speedup, I changed them to t and nil. But the reasoning
> behind this was weak. Users who need to speed up their agenda
> commands are most probably long-time users and they will be able
> to stumble on the variables and/or on the worg page.
> New users expect the agenda to keep agenda files folded when
> running an agenda command, and to dim blocked tasks by default.
> So -- this is now the case:
> (Note that it's by the same reasoning that
> `org-agenda-use-tag-inheritance' is set to (todo search timeline
> agenda) instead of nil, which would speed up most agendas.)
> Sorry for the instability here in master.
> I also set `org-time-clocksum-use-effort-durations' to nil by
> default, because it would surprise many users if they suddenly
> see new values in their clocktables.
> Thanks to Tassilo Horn and John Wiegley who let me rethink
> about all these defaults!
next prev parent reply other threads:[~2013-03-06 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 9:45 Agenda optimization (new worg page and new defaults) Bastien
2013-03-06 10:02 ` Carsten Dominik [this message]
2013-03-11 22:06 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).