From: Robert Horn <rjhorn@alum.mit.edu>
To: Eric S Fraga <esflists@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Agenda bug
Date: Tue, 06 Mar 2018 15:23:12 -0500 [thread overview]
Message-ID: <m3ina90x8v.fsf@alum.mit.edu> (raw)
In-Reply-To: <87lgf59kr6.fsf@gmail.com>
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: <times>
>>
>> cause agenda processing to fail. It tries to parse <times> 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
next prev parent reply other threads:[~2018-03-06 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 16:23 Agenda bug Robert Horn
2018-03-06 17:28 ` Eric S Fraga
2018-03-06 20:23 ` Robert Horn [this message]
2018-03-11 22:13 ` Nicolas Goaziou
2018-03-14 13:14 ` Robert Horn
-- strict thread matches above, loose matches on Subject: below --
2011-04-19 22:36 agenda bug Nicholas Putnam
2011-04-19 22:47 ` Nick Dokos
2011-04-20 0:15 ` Memnon Anon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ina90x8v.fsf@alum.mit.edu \
--to=rjhorn@alum.mit.edu \
--cc=emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=rjhorniii@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.