From: Carsten Dominik <firstname.lastname@example.org>
To: Andreas Amann <email@example.com>
Cc: Michael Brand <firstname.lastname@example.org>, email@example.com
Subject: Re: Surprising behaviour with agenda file
Date: Tue, 4 Oct 2011 14:33:51 +0200 [thread overview]
Message-ID: <6F1268CE-1D2D-4C51-8C7C-E3242DA27417@gmail.com> (raw)
This patch has now been accepted - I believe the performance hit will be minor.
I would like to know if this is not the case...
On Sep 29, 2011, at 5:48 PM, Andreas Amann wrote:
> On Thu, 29 Sep 2011 15:43:27 +0200, Michael Brand <firstname.lastname@example.org> wrote:
>> On Thu, Sep 29, 2011 at 15:25, Daniel Bausch <DanielBausch@gmx.de> wrote:
>>> It's not a bug, it's a feature (although I don't know what it's for -- maybe
>>> speed). However, there is a customizable option to switch it off:
>> Interesting. git blame and a list search leads quickly to this post
>> and thread that answers some questions:
> Okay, I see.
> In my opinion the current default is unsafe, since people can lose
> I propose to change the default of
> as below.
> commit 967ee90b3b05bad69b84fa3e5411f2d645121d6a
> Author: Andreas Amann <email@example.com>
> Date: Thu Sep 29 16:14:58 2011 +0100
> change default of org-agenda-skip-additional-timestamps-same-entry to nil
> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
> index b1fa5f5..20d55f7 100644
> --- a/lisp/org-agenda.el
> +++ b/lisp/org-agenda.el
> @@ -787,7 +787,7 @@ because you will take care of it on the day when scheduled."
> (const :tag "Remove prewarning if entry is scheduled" t)
> (integer :tag "Restart prewarning N days before deadline")))
> -(defcustom org-agenda-skip-additional-timestamps-same-entry t
> +(defcustom org-agenda-skip-additional-timestamps-same-entry nil
> "When nil, multiple same-day timestamps in entry make multiple agenda lines.
> When non-nil, after the search for timestamps has matched once in an
> entry, the rest of the entry will not be searched."
prev parent reply other threads:[~2011-10-04 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 12:16 Surprising behaviour with agenda file Andreas Amann
2011-09-29 13:25 ` Daniel Bausch
2011-09-29 13:43 ` Michael Brand
2011-09-29 15:48 ` Andreas Amann
2011-09-29 17:12 ` Sebastien Vauban
2011-10-04 12:33 ` Carsten Dominik [this message]
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).