From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Horn Subject: Re: Agenda bug Date: Tue, 06 Mar 2018 15:23:12 -0500 Message-ID: References: <87lgf59kr6.fsf@gmail.com> Reply-To: rjhorniii@gmail.com Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40700) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etJ7G-0006Z8-Kr for emacs-orgmode@gnu.org; Tue, 06 Mar 2018 15:23:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etJ7D-0001gy-HO for emacs-orgmode@gnu.org; Tue, 06 Mar 2018 15:23:18 -0500 Received: from mailbackend.panix.com ([166.84.1.89]:46804) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1etJ7D-0001fi-Dz for emacs-orgmode@gnu.org; Tue, 06 Mar 2018 15:23:15 -0500 In-reply-to: <87lgf59kr6.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: Eric S Fraga Cc: Org Mode List Eric S Fraga writes: > On Tuesday, 6 Mar 2018 at 11:23, Robert Horn wrote: >> I discovered that the lines ( the body of a headline): >> *** real headline >> * example >> :SCHEDULED: >> >> cause agenda processing to fail. It tries to parse as a >> timestamp. The parser used by agenda appears not to enforce the >> requirement that headlines begin with asterisks on the left margin. > > I think the issue is that SCHEDULED and DEADLINE entries must appear > immediately after the headline. You have a line (* example) in between > the SCHEDULED line and the headline. You have characterized the bug. That ":SCHEDULED:" should not have been considered a SCHEDULED entry. It should have been ignored, based on the description for org format in the manual. I was putting together an example for someone and was composing a full example of an org file. I just stumbled across this when trying various forms of verbatim, code, and other blocks. I was not expecting the agenda display and processing to completely fail. I created my example by eliminating one of the colons and explaining that in a real org file you would need the colon. But that leaves the bug that this particular error causes agenda creation to fail. I was expecting the parser to treat the SCHEDULED line as just more body text, and ignore it. -- Robert Horn rjhorniii@gmail.com