emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Christoph Groth <christoph@grothesque.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug? SCHEDULED lines treated differently when text precedes them
Date: Thu, 05 Sep 2019 15:00:59 +0200	[thread overview]
Message-ID: <877e6mew38.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874l1q9a9x.fsf@neron> (Christoph Groth's message of "Thu, 05 Sep 2019 14:51:06 +0200")

Hello,

Christoph Groth <christoph@grothesque.org> writes:

> With Org 9.2.3, the following two TODO items behave differently:
>
> ** TODO Something
> blabla
> SCHEDULED: <2019-09-01 Sun>
> [2019-09-05 Thu 14:39]
> ** TODO Something else
> SCHEDULED: <2019-09-01 Sun>
> foobar
> [2019-09-05 Thu 14:40]
>
> The first one behaves as expected, i.e. it appears in today's
> (2019-09-05) agenda, since it's not done yet.
>
> The second one does appear in today's agenda, but it is visible for the
> day 2019-09-01.
>
> Is this behavior by design?  If yes, could someone please explain the
> rationale or point me to relevant documentation or discussions?

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.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2019-09-05 13:01 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 [this message]
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

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=877e6mew38.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=christoph@grothesque.org \
    --cc=emacs-orgmode@gnu.org \
    /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

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).