From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug? SCHEDULED lines treated differently when text precedes them
Date: Fri, 06 Sep 2019 10:52:00 +1000 [thread overview]
Message-ID: <87pnkeb61b.fsf@gmail.com> (raw)
In-Reply-To: <87zhjiamo2.fsf@neron>
You may also find the command M-x org-lint useful. I regularly run it on
my larger org files after an org release to spot problems in my org
files (either due to my error or changes in orgmode)
Tim
Christoph Groth <christoph@grothesque.org> writes:
> Nicolas Goaziou wrote:
>
>> Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must
>> appear right after the headline, per Org syntax. This is specified at
>> the first paragraph in (info "(org) Deadlines and Scheduling").
>>
>> Elswhere, only the timestamp is meaningful to Org.
>
> Thanks for the quick clarification! I didn't see the relevant line in
> the documentation since my Emacs from Debian shows only the info
> documentation for the (outdated) Org that is bundled with Emacs [1].
>
> I understand now that Org does what it should. However, I find this
> behavior quite dangerous. It caught me after more than 10 years of
> using Org. If there's a list of long-term issues with Org somewhere,
> this problem may deserve being added to it.
>
> Cheers
> Christoph
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725408
--
Tim Cross
prev parent reply other threads:[~2019-09-06 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:51 Bug? SCHEDULED lines treated differently when text precedes them Christoph Groth
2019-09-05 13:00 ` Nicolas Goaziou
2019-09-05 13:38 ` Christoph Groth
2019-09-05 13:40 ` Nicolas Goaziou
2019-09-05 13:58 ` Christoph Groth
2019-09-06 1:08 ` Tim Cross
2019-09-05 14:02 ` Carsten Dominik
2019-09-06 0:52 ` Tim Cross [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnkeb61b.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).