From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: DEADLINE: position in entry Date: Wed, 9 Nov 2016 20:37:00 +1100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c1995e2ba35af0540dafff7 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44837) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4PJa-0005J2-Gk for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 04:37:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4PJW-0003ko-9b for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 04:37:06 -0500 Received: from mail-yb0-x233.google.com ([2607:f8b0:4002:c09::233]:33157) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4PJW-0003kf-4X for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 04:37:02 -0500 Received: by mail-yb0-x233.google.com with SMTP id o7so76298028ybb.0 for ; Wed, 09 Nov 2016 01:37:01 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode --94eb2c1995e2ba35af0540dafff7 Content-Type: text/plain; charset=UTF-8 Is this the way it should be? The first DEADLINE: shows up both as a warning and on the due date in the agenda, but the second one does not. It only works for me if the DEADLINE: is the first line after the heading. Version 9, emacs 24 *** test 1 DEADLINE: <2016-11-19 Sat> *** test 2 DEADLINE: <2016-11-19 Sat> Thanks, Alan -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c1995e2ba35af0540dafff7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Is this the way it should be? The first DEADLINE: shows up= both as a warning and on the due date in the agenda, but the second one do= es not. It only works for me if the DEADLINE: is the first line after the h= eading. Version 9, emacs 24

*** test 1=C2=A0=C2= =A0
DEADLINE: <2016-11-19 Sat>

*** test 2

DEADLINE:= <2016-11-19 Sat>


Thanks,
Alan


--
= Alan L Tyree=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 htt= p://austlii.edu.au/~alan
Tel:=C2=A0 04 2748 6206=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sip:typhoon@iptel.org
--94eb2c1995e2ba35af0540dafff7-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Wahl Subject: Re: DEADLINE: position in entry Date: Wed, 09 Nov 2016 15:20:26 +0100 Message-ID: <84twbg7n11.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59744) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4Tkx-0006YP-LV for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 09:21:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4Tks-000690-MF for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 09:21:39 -0500 Received: from [195.159.176.226] (port=38816 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4Tks-00068f-Ee for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 09:21:34 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1c4TkE-0000Mq-0F for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 15:20:54 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hi! Alan Tyree writes: > Is this the way it should be? The first DEADLINE: shows up both as a > warning and on the due date in the agenda, but the second one does not. It > only works for me if the DEADLINE: is the first line after the heading. > Version 9, emacs 24 > > *** test 1 > DEADLINE: <2016-11-19 Sat> > > *** test 2 > > DEADLINE: <2016-11-19 Sat> > > > Thanks, > Alan Currently http://orgmode.org/worg/dev/org-syntax.html says: A planning is an element with the following pattern: HEADLINE PLANNING (and DEADLINE is e.g. a PLANNING) ... In particular, no blank line is allowed between PLANNING and HEADLINE. So your example 'test 2' does not have a DEADLINE according to the org-syntax document. Ciao, -- Marco From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philip Hudson Subject: Re: DEADLINE: position in entry Date: Wed, 9 Nov 2016 18:51:10 +0000 Message-ID: References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4Xy9-0000lt-0W for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 13:51:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4Xy8-0000wD-6p for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 13:51:33 -0500 Received: from mail-vk0-x234.google.com ([2607:f8b0:400c:c05::234]:35514) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4Xy8-0000vT-1E for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 13:51:32 -0500 Received: by mail-vk0-x234.google.com with SMTP id w194so183610114vkw.2 for ; Wed, 09 Nov 2016 10:51:31 -0800 (PST) In-Reply-To: <84twbg7n11.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Marco Wahl Cc: emacs orgmode-mailinglist On 9 November 2016 at 14:20, Marco Wahl wrote: > In particular, no blank line is allowed between PLANNING and HEADLINE. I just checked, and was surprised to find that M-x org-lint RET does *not* catch this. Is this a bug in org-lint, or does org-lint not intend to catch this sort of thing? -- Phil Hudson http://hudson-it.ddns.net Pretty Good Privacy (PGP) ID: 0x887DCA63 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan L Tyree Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 07:42:30 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46543) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4Zhh-00078W-H0 for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 15:42:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4Zhd-0007aM-HM for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 15:42:41 -0500 Received: from mail-pf0-x230.google.com ([2607:f8b0:400e:c00::230]:33398) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4Zhd-0007aF-9u for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 15:42:37 -0500 Received: by mail-pf0-x230.google.com with SMTP id d2so132493140pfd.0 for ; Wed, 09 Nov 2016 12:42:37 -0800 (PST) Received: from [192.168.1.100] (202.63.32.163.static.rev.eftel.com. [202.63.32.163]) by smtp.googlemail.com with ESMTPSA id 186sm1302728pfv.61.2016.11.09.12.42.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Nov 2016 12:42:35 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org On 10/11/16 05:51, Philip Hudson wrote: > On 9 November 2016 at 14:20, Marco Wahl wrote: >> In particular, no blank line is allowed between PLANNING and HEADLINE. > I just checked, and was surprised to find that M-x org-lint RET does > *not* catch this. Is this a bug in org-lint, or does org-lint not > intend to catch this sort of thing? > > Also, if this really is the case, then the manual needs to be modified. Under 8.1, it says " A timestamp can appear anywhere in the headline or body of an Org tree entry." and under 8.3: "A timestamp may be preceded by special keywords to facilitate planning:" I can't see anywhere that requires the DEADLINE: keyword to be flush against a heading. There may be some reason for requiring this, but if there is no good reason, I would like to see it changed to be more flexible. Alan -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 00:29:43 +0100 Message-ID: <87inrwi654.fsf@nicolasgoaziou.fr> References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4cJL-0003ZQ-8g for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:29:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4cJK-0001M8-EB for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:29:43 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:51580) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c4cJK-0001LU-8U for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:29:42 -0500 In-Reply-To: (Philip Hudson's message of "Wed, 9 Nov 2016 18:51:10 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Philip Hudson Cc: Marco Wahl , emacs orgmode-mailinglist Hello, Philip Hudson writes: > On 9 November 2016 at 14:20, Marco Wahl wrote: >> In particular, no blank line is allowed between PLANNING and HEADLINE. > > I just checked, and was surprised to find that M-x org-lint RET does > *not* catch this. Is this a bug in org-lint, or does org-lint not > intend to catch this sort of thing? It was a bug in the parser, which was more tolerant than necessary. This is fixed. Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 00:36:24 +0100 Message-ID: <87eg2ki5tz.fsf@nicolasgoaziou.fr> References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33045) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4cPq-0006A3-Af for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:36:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4cPn-0004bz-1t for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:36:26 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:46152) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c4cPm-0004bH-SY for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:36:22 -0500 In-Reply-To: (Alan L. Tyree's message of "Thu, 10 Nov 2016 07:42:30 +1100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan L Tyree Cc: emacs-orgmode@gnu.org Hello, Alan L Tyree writes: > On 10/11/16 05:51, Philip Hudson wrote: > Also, if this really is the case, then the manual needs to be > modified. Under 8.1, it says > > " A timestamp can appear anywhere in the headline or body of an Org tree > entry." Section 8.1 is about regular time-stamps, which are not necessarily tied to DEADLINE and SCHEDULED keyword. Therefore, the sentence above is true. > and under 8.3: > > "A timestamp may be preceded by special keywords to facilitate planning:" > > I can't see anywhere that requires the DEADLINE: keyword to be flush > against a heading. This is in 8.3.1, first footnote. Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 10:44:52 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> <87eg2ki5tz.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c07e550ea4c040540e6d732 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34547) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4cY6-0000w6-Pn for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:45:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4cY1-0000yv-Iy for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:44:58 -0500 Received: from mail-yw0-x22c.google.com ([2607:f8b0:4002:c05::22c]:33118) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4cY1-0000yZ-ED for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:44:53 -0500 Received: by mail-yw0-x22c.google.com with SMTP id r204so226394566ywb.0 for ; Wed, 09 Nov 2016 15:44:53 -0800 (PST) In-Reply-To: <87eg2ki5tz.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan L Tyree , emacs-orgmode --94eb2c07e550ea4c040540e6d732 Content-Type: text/plain; charset=UTF-8 On 10 November 2016 at 10:36, Nicolas Goaziou wrote: > Hello, > > Alan L Tyree writes: > > > On 10/11/16 05:51, Philip Hudson wrote: > > > Also, if this really is the case, then the manual needs to be > > modified. Under 8.1, it says > > > > " A timestamp can appear anywhere in the headline or body of an Org tree > > entry." > > Section 8.1 is about regular time-stamps, which are not necessarily tied > to DEADLINE and SCHEDULED keyword. Therefore, the sentence above is > true. > > > and under 8.3: > > > > "A timestamp may be preceded by special keywords to facilitate planning:" > > > > I can't see anywhere that requires the DEADLINE: keyword to be flush > > against a heading. > > This is in 8.3.1, first footnote. > > So it is. Not exactly prominent :-). I still think the manual is misleading, and is there some reason that "planning" items are treated different from plain old appointment timestamps? I just seems (to a non-programmer) to be an unnecessary restriction. Cheers, Alan > Regards, > > -- > Nicolas Goaziou > -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c07e550ea4c040540e6d732 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 10 November 2016 at 10:36, Nicolas Goaziou <mail@nicolasgoazio= u.fr> wrote:
Hello,

Alan L Tyree <alantyree@gmail.com= > writes:

> On 10/11/16 05:51, Philip Hudson wrote:

> Also, if this really is the case, then the man= ual needs to be
> modified. Under 8.1, it says
>
> " A timestamp can appear anywhere in the headline or body of an O= rg tree
> entry."

Section 8.1 is about regular time-stamps, which are not necessarily = tied
to DEADLINE and SCHEDULED keyword. Therefore, the sentence above is
true.

> and under 8.3:
>
> "A timestamp may be preceded by special keywords to facilitate pl= anning:"
>
> I can't see anywhere that requires the DEADLINE: keyword to be flu= sh
> against a heading.

This is in 8.3.1, first footnote.

So it is. Not exactly prominent :-). I still think th= e manual is misleading, and is there some reason that "planning" = items are treated different from plain old appointment timestamps? I just s= eems (to a non-programmer) to be an unnecessary restriction.

<= div>Cheers,
Alan
=C2=A0
Regards,

--
Nicolas Goaziou



--
A= lan L Tyree=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 http:= //austlii.edu.au/~alan
Tel:=C2=A0 04 2748 6206=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sip:typhoon@iptel.org
--94eb2c07e550ea4c040540e6d732-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: DEADLINE: position in entry Date: Wed, 9 Nov 2016 16:47:17 -0700 Message-ID: References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34962) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4caO-0001dD-CF for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:47:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4caN-0002Bh-De for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:47:20 -0500 Received: from mail-ua0-x22e.google.com ([2607:f8b0:400c:c08::22e]:34983) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4caN-0002BL-9C for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:47:19 -0500 Received: by mail-ua0-x22e.google.com with SMTP id 12so187657743uas.2 for ; Wed, 09 Nov 2016 15:47:19 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan L Tyree Cc: emacs-orgmode@gnu.org iirc we've discussed whether planning lines (i.e. scheduled, deadline, closed at this time) should be flexible. we concluded to make them strict. check archives for the discussion. :) everything goes through this mailing list. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. And ANYBODY can get it. Denmark: free Karina Hansen NOW. UPDATE 2016-10: home, but not fully free From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 10:59:49 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0970b86830500540e70db5 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37592) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4cmW-00057k-O4 for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:59:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4cmV-0008Qa-OP for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:59:52 -0500 Received: from mail-yb0-x22c.google.com ([2607:f8b0:4002:c09::22c]:36303) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4cmV-0008QC-FW for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:59:51 -0500 Received: by mail-yb0-x22c.google.com with SMTP id v78so83580863ybe.3 for ; Wed, 09 Nov 2016 15:59:51 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Samuel Wales Cc: emacs-orgmode --94eb2c0970b86830500540e70db5 Content-Type: text/plain; charset=UTF-8 On 10 November 2016 at 10:47, Samuel Wales wrote: > iirc we've discussed whether planning lines (i.e. scheduled, deadline, > closed at this time) should be flexible. we concluded to make them > strict. > > check archives for the discussion. :) everything goes through this > mailing list. > > OK, I'll accept that and have a look at the rationale. However, since DEADLINE: is so terribly important, I think that there should be a prominent warning in the manual that they are simply ignored if not positioned correctly. Warnings should appear, at the very least, in 8.1 and 8.3. Suggested wording: In 8.1: timestamp can appear anywhere in the headline or body of an Org tree entr UNLESS is is preceded by a keyword in which case it must be properly positioned or it will be ignored: see 8.3 for details. In 8.3: A timestamp may be preceded by special keywords to facilitate planning. WARNING: both the timestamp and the keyword are ignored if not positioned immediately following the headline. No space or other text is allowed. Regards, Alan > -- > The Kafka Pandemic: http://thekafkapandemic.blogspot.com > > The disease DOES progress. MANY people have died from it. And > ANYBODY can get it. > > Denmark: free Karina Hansen NOW. > UPDATE 2016-10: home, but not fully free > -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c0970b86830500540e70db5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 10 November 2016 at 10:47, Samuel Wales <samologist@gmail.com> wrote:
ii= rc we've discussed whether planning lines (i.e. scheduled, deadline, closed at this time) should be flexible.=C2=A0 we concluded to make them strict.

check archives for the discussion.=C2=A0 :) everything goes through this mailing list.

OK, I'll accept that and have a look at the rationale. Ho= wever, since DEADLINE: is so terribly important, I think that there should = be a prominent warning in the manual that they are simply ignored if not po= sitioned correctly. Warnings should appear, at the very least, in 8.1 and 8= .3.

Suggested wording:

In 8.1:

<= br>timestamp can appear anywhere in the headline or body of an Org tree
= entr UNLESS is is preceded by a keyword in which case it must be properly p= ositioned or it will be ignored: see 8.3 for details.



--
Alan L Tyree=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://austlii.edu.au/~alan
Tel:= =C2=A0 04 2748 6206=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 s= ip:typhoon@iptel.org
--94eb2c0970b86830500540e70db5-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 16:08:34 +0100 Message-ID: <87wpgbgyod.fsf@nicolasgoaziou.fr> References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4qxu-0006aY-NT for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 10:08:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4qxt-0007PH-St for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 10:08:34 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:59232) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c4qxt-0007Nu-N3 for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 10:08:33 -0500 In-Reply-To: (Alan Tyree's message of "Thu, 10 Nov 2016 10:59:49 +1100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan Tyree Cc: emacs-orgmode Hello, Alan Tyree writes: > Suggested wording: > > In 8.1: > > > timestamp can appear anywhere in the headline or body of an Org tree > entr UNLESS is is preceded by a keyword in which case it must be properly > positioned or it will be ignored: see 8.3 for details. This is wrong. Only the keyword is ignored, not the timestamp. This is why DEADLINE and SCHEDULED location is unrelated to section 8.1. > A timestamp may be preceded by special keywords to facilitate planning. > WARNING: both the timestamp and the keyword are ignored if not positioned > immediately following the headline. No space or other text is allowed. I think "immediately following the headline" is unambiguous. No need to specify "no space or other text is allowed". I modified section 8.3 accordingly. WDYT? Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: Re: DEADLINE: position in entry Date: Fri, 11 Nov 2016 08:05:29 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> <87wpgbgyod.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c08581ac94f3c0540f8bb49 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57163) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4wXO-0000qq-Jr for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 16:05:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4wXM-00086K-SG for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 16:05:34 -0500 Received: from mail-yw0-x22f.google.com ([2607:f8b0:4002:c05::22f]:33810) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4wXM-00085p-Nj for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 16:05:32 -0500 Received: by mail-yw0-x22f.google.com with SMTP id t125so259361916ywc.1 for ; Thu, 10 Nov 2016 13:05:31 -0800 (PST) In-Reply-To: <87wpgbgyod.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan Tyree , Samuel Wales , emacs-orgmode --94eb2c08581ac94f3c0540f8bb49 Content-Type: text/plain; charset=UTF-8 On 11 November 2016 at 02:08, Nicolas Goaziou wrote: > Hello, > > Alan Tyree writes: > > > Suggested wording: > > > > In 8.1: > > > > > > timestamp can appear anywhere in the headline or body of an Org tree > > entr UNLESS is is preceded by a keyword in which case it must be properly > > positioned or it will be ignored: see 8.3 for details. > > This is wrong. Only the keyword is ignored, not the timestamp. This is > why DEADLINE and SCHEDULED location is unrelated to section 8.1. > Hi Nicolas, Will you please double check this? On my system, the entry does *not* show up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show up. So, for the important purpose under discussion, the timestamp is ignored. Emacs version 24.4.1 on Debian Stable org-version: Org mode version 9.0 (9.0-elpaplus @ /home/alant/.emacs.d/elpa/org-plus-contrib-20161102/) > > > A timestamp may be preceded by special keywords to facilitate planning. > > WARNING: both the timestamp and the keyword are ignored if not positioned > > immediately following the headline. No space or other text is allowed. > > I think "immediately following the headline" is unambiguous. No need to > specify "no space or other text is allowed". > > I modified section 8.3 accordingly. > > WDYT? > > Subject to the above, OK. Just so long as there is a good strong warning about it. Thanks, Alan Regards, > > -- > Nicolas Goaziou > -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c08581ac94f3c0540f8bb49 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 11 November 2016 at 02:08, Nicolas Goaziou <mail@nicolasgoazio= u.fr> wrote:
Hello,

Alan Tyree <alantyree@gmail.com> writes:

> Suggested wording:
>
> In 8.1:
>
>
> timestamp can appear anywhere in the headline or body of an Org tree > entr UNLESS is is preceded by a keyword in which case it must be prope= rly
> positioned or it will be ignored: see 8.3 for details.

This is wrong. Only the keyword is ignored, not the timestamp. This = is
why DEADLINE and SCHEDULED location is unrelated to section 8.1.

Hi Nicolas,
Will you please double = check this? On my system, the entry does *not* show up in the agenda (C-c a= a). If I remove the DEADLINE:, then it does show up. So, for the important= purpose under discussion, the timestamp is ignored.

Emac= s version 24.4.1 on Debian Stable

org-version: Org mode v= ersion 9.0 (9.0-elpaplus @ /home/alant/.emacs.d/elpa/org-plus-contrib-20161= 102/)


=C2=A0

> A timestamp may be preceded by special keywords to facilitate planning= .
> WARNING: both the timestamp and the keyword are ignored if not positio= ned
> immediately following the headline. No space or other text is allowed.=

I think "immediately following the headline" is unambiguou= s. No need to
specify "no space or other text is allowed".

I modified section 8.3 accordingly.

WDYT?

Subject to the above, OK. Just so long as there is a = good strong warning about it.
=C2=A0
Thanks,
Alan

Regards,

--
Nicolas Goaziou



--
Alan L Tyree=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://austlii.edu.au/~alan
Tel:= =C2=A0 04 2748 6206=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 s= ip:typhoon@iptel.org
--94eb2c08581ac94f3c0540f8bb49-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: DEADLINE: position in entry Date: Fri, 11 Nov 2016 01:12:28 +0100 Message-ID: <8737iyho2b.fsf@nicolasgoaziou.fr> References: <84twbg7n11.fsf@gmail.com> <87wpgbgyod.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4zSG-0001u9-1p for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 19:12:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4zSF-0002rH-Ah for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 19:12:28 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:41851) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c4zSF-0002qm-3g for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 19:12:27 -0500 In-Reply-To: (Alan Tyree's message of "Fri, 11 Nov 2016 08:05:29 +1100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan Tyree Cc: emacs-orgmode Alan Tyree writes: > Will you please double check this? On my system, the entry does *not* show > up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show > up. So, for the important purpose under discussion, the timestamp is > ignored. You are right, the timestamp was ignored, but that's a bug. I fixed it. Thank you. Regards, From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: Re: DEADLINE: position in entry Date: Fri, 11 Nov 2016 12:52:34 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> <87wpgbgyod.fsf@nicolasgoaziou.fr> <8737iyho2b.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0a7cd878abd20540fcbe41 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58134) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c511B-00050m-NS for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 20:52:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c511A-0004A3-FW for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 20:52:37 -0500 Received: from mail-yw0-x234.google.com ([2607:f8b0:4002:c05::234]:35372) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c511A-000480-7f for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 20:52:36 -0500 Received: by mail-yw0-x234.google.com with SMTP id i145so1993989ywg.2 for ; Thu, 10 Nov 2016 17:52:36 -0800 (PST) In-Reply-To: <8737iyho2b.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alan Tyree , Samuel Wales , emacs-orgmode --94eb2c0a7cd878abd20540fcbe41 Content-Type: text/plain; charset=UTF-8 On 11 November 2016 at 11:12, Nicolas Goaziou wrote: > Alan Tyree writes: > > > Will you please double check this? On my system, the entry does *not* > show > > up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show > > up. So, for the important purpose under discussion, the timestamp is > > ignored. > > You are right, the timestamp was ignored, but that's a bug. I fixed it. > Thank you. > > Regards, > Glad it is all cleared up. Thanks for a great piece of software! Alan -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c0a7cd878abd20540fcbe41 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 11 November 2016 at 11:12, Nicolas Goaziou <mail@nicolasgoazio= u.fr> wrote:
Alan Tyree <alantyree@gmail.co= m> writes:

> Will you please double check this? On my system, the entry does *not* = show
> up in the agenda (C-c a a). If I remove the DEADLINE:, then it does sh= ow
> up. So, for the important purpose under discussion, the timestamp is > ignored.

You are right, the timestamp was ignored, but that's a bug. I fi= xed it.
Thank you.

Regards,

Glad it is all cleared up. Thanks for a great piece = of software!
Alan
--
Alan L Tyree=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://austlii.edu.au/~alan
Tel:=C2=A0 04 2748 6206= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sip:typhoon@iptel.org=
--94eb2c0a7cd878abd20540fcbe41-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yasushi SHOJI Subject: Re: DEADLINE: position in entry Date: Mon, 21 Nov 2016 14:10:52 +0900 Message-ID: <8737ilifj7.wl@dns1.atmark-techno.com> References: Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c8gsn-0007BZ-Km for emacs-orgmode@gnu.org; Mon, 21 Nov 2016 00:11:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c8gsi-0005qN-Md for emacs-orgmode@gnu.org; Mon, 21 Nov 2016 00:11:09 -0500 Received: from p654789.hkidff01.ap.so-net.ne.jp ([121.101.71.137]:49984 helo=gw.atmark-techno.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c8gsi-0005q7-D3 for emacs-orgmode@gnu.org; Mon, 21 Nov 2016 00:11:04 -0500 Received: from mail-pg0-f70.google.com (mail-pg0-f70.google.com [74.125.83.70]) by gw.atmark-techno.com (Postfix) with ESMTPS id 9CDB52036C for ; Mon, 21 Nov 2016 14:11:00 +0900 (JST) Received: by mail-pg0-f70.google.com with SMTP id 3so374618513pgd.3 for ; Sun, 20 Nov 2016 21:11:00 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org On Wed, 09 Nov 2016 18:37:00 +0900, Alan Tyree wrote: > > Is this the way it should be? The first DEADLINE: shows up both as a > warning and on the due date in the agenda, but the second one does > not. It only works for me if the DEADLINE: is the first line after the > heading. Version 9, emacs 24 > > *** test 1 > DEADLINE: <2016-11-19 Sat> > > *** test 2 > > DEADLINE: <2016-11-19 Sat> at release_9.0.1-47-gb062593 with the following org file, org-agenda shows the closed entry. Is this also related? Yes, org-lint complains about the 4th "scheduled" line saying: "Misplaced planning info line", but isn't deadline planning info line? is any of planning info line not allowed in the body? ---- >8 ---- cut ---- >8 ---- * DONE org DEADLINE: [2016-01-07 Thu 17:39] SCHEDULED: <2015-09-29 Tue .+1w> ---- >8 ---- cut ---- >8 ---- ; /tmp/a.el (add-to-list 'load-path "~/src/org-mode/lisp") (setq org-agenda-files '("/tmp/a.org")) ---- >8 ---- cut ---- >8 ---- $ emacs -Q -l /tmp/a.el -f 'org-agenda' -- yashi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: DEADLINE: position in entry Date: Mon, 21 Nov 2016 19:08:55 +0100 Message-ID: References: <8737ilifj7.wl@dns1.atmark-techno.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: "Emacs-orgmode" To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Yasushi SHOJI writes: > Alan Tyree wrote: >> >> Is this the way it should be? The first DEADLINE: shows up both as a >> warning and on the due date in the agenda, but the second one does >> not. It only works for me if the DEADLINE: is the first line after the >> heading. Version 9, emacs 24 >> >> *** test 1 >> DEADLINE: <2016-11-19 Sat> >> >> *** test 2 >> >> DEADLINE: <2016-11-19 Sat> > > at release_9.0.1-47-gb062593 with the following org file, org-agenda > shows the closed entry. Is this also related? > > Yes, org-lint complains about the 4th "scheduled" line saying: > "Misplaced planning info line", but isn't deadline planning info line? > is any of planning info line not allowed in the body? > > ---- >8 ---- cut ---- >8 ---- > * DONE org > DEADLINE: [2016-01-07 Thu 17:39] > > SCHEDULED: <2015-09-29 Tue .+1w> > > ---- >8 ---- cut ---- >8 ---- A shoot in the dark: replace the [] by <>. [] for DEADLINE does not make much sense... -- Sebastien Vauban From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yasushi SHOJI Subject: Re: DEADLINE: position in entry Date: Wed, 23 Nov 2016 17:09:35 +0900 Message-ID: References: <8737ilifj7.wl@dns1.atmark-techno.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1145388ee0404c0541f368d2 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50616) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9Scc-0006M8-6O for emacs-orgmode@gnu.org; Wed, 23 Nov 2016 03:09:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9Scb-0002ag-2N for emacs-orgmode@gnu.org; Wed, 23 Nov 2016 03:09:38 -0500 Received: from mail-io0-x22c.google.com ([2607:f8b0:4001:c06::22c]:34026) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c9Sca-0002aA-UD for emacs-orgmode@gnu.org; Wed, 23 Nov 2016 03:09:37 -0500 Received: by mail-io0-x22c.google.com with SMTP id c21so11166965ioj.1 for ; Wed, 23 Nov 2016 00:09:36 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Sebastien Vauban Cc: emacs-orgmode@gnu.org --001a1145388ee0404c0541f368d2 Content-Type: text/plain; charset=UTF-8 Hi, On Tue, Nov 22, 2016 at 3:08 AM, Sebastien Vauban wrote: > > Yasushi SHOJI writes: > > ---- >8 ---- cut ---- >8 ---- > > * DONE org > > DEADLINE: [2016-01-07 Thu 17:39] > > > > SCHEDULED: <2015-09-29 Tue .+1w> > > > > ---- >8 ---- cut ---- >8 ---- > > A shoot in the dark: replace the [] by <>. > > [] for DEADLINE does not make much sense... thanks for your comment. chainging the inactive timestamp to active doesn't seem to change the behavior. even with an inactive time stamp, it's not a good excuse to show a closed entry, isn't it? -- yashi --001a1145388ee0404c0541f368d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

On Tue, Nov 22, 2016 at 3:08 AM, Sebastien Vaub= an <sva-news@mygooglest.com> wrote:
>
> Yasushi SHOJI <yashi@atmark-techno.com> writes:
> > ---- &= gt;8 ---- cut ---- >8 ----
> > * DONE org
> > =C2=A0 D= EADLINE: [2016-01-07 Thu 17:39]
> >
> > =C2=A0 SCHEDULED:= <2015-09-29 Tue .+1w>
> >
> > ---- >8 ---- cut = ---- >8 ----
>
> A shoot in the dark: replace the [] by <= >.
>
> [] for DEADLINE does not make much sense...

th= anks for your comment.
chainging the inactive timestamp to active d= oesn't seem
to change the behavior.

<= div>even with an inactive time stamp, it's not a good excuse
= to show a closed entry, isn't it?
--=C2=A0
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 yashi

--001a1145388ee0404c0541f368d2-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: DEADLINE: position in entry Date: Fri, 25 Nov 2016 12:24:31 +0100 Message-ID: <87vavbztsg.fsf@nicolasgoaziou.fr> References: <8737ilifj7.wl@dns1.atmark-techno.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57700) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cAEcO-00026v-Bx for emacs-orgmode@gnu.org; Fri, 25 Nov 2016 06:24:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cAEcI-0001Vn-Ml for emacs-orgmode@gnu.org; Fri, 25 Nov 2016 06:24:36 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:54896) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cAEcI-0001VZ-GK for emacs-orgmode@gnu.org; Fri, 25 Nov 2016 06:24:30 -0500 In-Reply-To: (Yasushi SHOJI's message of "Wed, 23 Nov 2016 17:09:35 +0900") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Yasushi SHOJI Cc: Sebastien Vauban , emacs-orgmode@gnu.org Hello, Yasushi SHOJI writes: > On Tue, Nov 22, 2016 at 3:08 AM, Sebastien Vauban > wrote: >> >> Yasushi SHOJI writes: >> > ---- >8 ---- cut ---- >8 ---- >> > * DONE org >> > DEADLINE: [2016-01-07 Thu 17:39] >> > >> > SCHEDULED: <2015-09-29 Tue .+1w> >> > >> > ---- >8 ---- cut ---- >8 ---- >> >> A shoot in the dark: replace the [] by <>. >> >> [] for DEADLINE does not make much sense... > > thanks for your comment. > chainging the inactive timestamp to active doesn't seem > to change the behavior. > > even with an inactive time stamp, it's not a good excuse > to show a closed entry, isn't it? I cannot reproduce your problem? Could you try with -Q (and a minimal Org configuration)? Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yasushi SHOJI Subject: Re: DEADLINE: position in entry Date: Tue, 29 Nov 2016 16:54:24 +0900 Message-ID: <87zikivhzj.wl@dns1.atmark-techno.com> References: <8737ilifj7.wl@dns1.atmark-techno.com> <87vavbztsg.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: multipart/mixed; boundary="Multipart_Tue_Nov_29_16:54:24_2016-1" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42743) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBdFR-0003Cg-NZ for emacs-orgmode@gnu.org; Tue, 29 Nov 2016 02:54:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cBdFO-0003nF-Hl for emacs-orgmode@gnu.org; Tue, 29 Nov 2016 02:54:41 -0500 Received: from p654789.hkidff01.ap.so-net.ne.jp ([121.101.71.137]:47932 helo=gw.atmark-techno.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBdFO-0003ly-8m for emacs-orgmode@gnu.org; Tue, 29 Nov 2016 02:54:38 -0500 Received: from mail-pg0-f71.google.com (mail-pg0-f71.google.com [74.125.83.71]) by gw.atmark-techno.com (Postfix) with ESMTPS id 38506202A9 for ; Tue, 29 Nov 2016 16:54:35 +0900 (JST) Received: by mail-pg0-f71.google.com with SMTP id q10so412318359pgq.7 for ; Mon, 28 Nov 2016 23:54:34 -0800 (PST) In-Reply-To: <87vavbztsg.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org --Multipart_Tue_Nov_29_16:54:24_2016-1 Content-Type: text/plain; charset=US-ASCII Hi Nicolas, On Fri, 25 Nov 2016 20:24:31 +0900, Nicolas Goaziou wrote: > > I cannot reproduce your problem? Could you try with -Q (and a minimal > Org configuration)? Hmm... That's what I did and got the following: Week-agenda (W48): Monday 28 November 2016 W48 a: DONE org Tuesday 29 November 2016 a: DONE org Wednesday 30 November 2016 a: DONE org Let me try again. $ cd ~/src/org-mode $ git describe release_9.0.1-74-g3d80b35 $ make clean autoloads $ ~/src/emacs25/src/emacs -Q -l /tmp/a.el -f 'org-agenda' now I get Week-agenda (W48): Monday 28 November 2016 W48 Tuesday 29 November 2016 a: DONE org Wednesday 30 November 2016 Thursday 1 December 2016 Friday 2 December 2016 Saturday 3 December 2016 Sunday 4 December 2016 the commit 4b99ed5e seems to change the output a bit. But I still get the done entry. I'm attaching those two files (just in case) but the contents are: /tmp/a.el: (add-to-list 'load-path "~/src/org-mode/lisp") (setq org-agenda-files '("/tmp/a.org")) /tmp/a.org: * DONE org DEADLINE: [2016-01-07 Thu 17:39] SCHEDULED: <2015-09-29 Tue .+1w> BTW, I'm on "GNU Emacs 25.1.90.1 (x86_64-pc-linux-gnu) of 2016-11-29", if it mutters. $ cd ~/src/emacs25 $ git describe emacs-24.5-rc3-fixed-8534-gf6da597 Let me know if you need any other info. Thanks, -- yashi --Multipart_Tue_Nov_29_16:54:24_2016-1 Content-Type: text/plain; type=emacs-lisp; charset=UTF-8; name="a.el" Content-Disposition: attachment; filename="a.el" Content-Transfer-Encoding: quoted-printable (add-to-list 'load-path "~/src/org-mode/lisp") (setq org-agenda-files '("/tmp/a.org")) --Multipart_Tue_Nov_29_16:54:24_2016-1 Content-Type: text/plain; name="a.org"; charset=US-ASCII Content-Disposition: attachment; filename="a.org" Content-Transfer-Encoding: quoted-printable * DONE org DEADLINE: [2016-01-07 Thu 17:39] SCHEDULED: <2015-09-29 Tue .+1w> --Multipart_Tue_Nov_29_16:54:24_2016-1-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: DEADLINE: position in entry Date: Tue, 29 Nov 2016 09:35:44 +0100 Message-ID: <87wpfmel9b.fsf@nicolasgoaziou.fr> References: <8737ilifj7.wl@dns1.atmark-techno.com> <87vavbztsg.fsf@nicolasgoaziou.fr> <87zikivhzj.wl@dns1.atmark-techno.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59857) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBdtD-0001vz-25 for emacs-orgmode@gnu.org; Tue, 29 Nov 2016 03:35:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cBdt9-0002aH-Su for emacs-orgmode@gnu.org; Tue, 29 Nov 2016 03:35:47 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:41760) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cBdt9-0002Zs-G3 for emacs-orgmode@gnu.org; Tue, 29 Nov 2016 03:35:43 -0500 In-Reply-To: <87zikivhzj.wl@dns1.atmark-techno.com> (Yasushi SHOJI's message of "Tue, 29 Nov 2016 16:54:24 +0900") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Yasushi SHOJI Cc: emacs-orgmode@gnu.org Hello, Yasushi SHOJI writes: > /tmp/a.org: > * DONE org > DEADLINE: [2016-01-07 Thu 17:39] > > SCHEDULED: <2015-09-29 Tue .+1w> OK. I get it. Since SCHEDULED: keyword is misplaced, it is ignored. However, the repeating time-stamp is not. Org really sees something like, XXXXXXXX <2015-09-29 Tue .+1w> which is equivalent to adding a plain time-stamp in the entry, and, therefore, display it. Regards, -- Nicolas Goaziou