From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Igor Katson <igor.katson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: In org-mode 9 "Scheduled" and "Deadline" are no longer parsed if they are not in the beginning
Date: Tue, 19 Jun 2018 16:44:46 +0200 [thread overview]
Message-ID: <87muvqesyp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALE8M=7ojd+Nh2yFfALFKTkwE1gw4GoOZ8wfceJmPUCV7hV_xA@mail.gmail.com> (Igor Katson's message of "Tue, 19 Jun 2018 07:37:08 -0700")
Hello,
Igor Katson <igor.katson@gmail.com> writes:
> I've been using org-mode for years, and somewhere between version 8 and 9,
> a change happened, which I could not find in the changelogs.
>
> Here's how I often used to format TODO items which are scheduled:
>
> * TODO Item
> some-text
> some-more-text
> SCHEDULED: <2018-06-19 Tue>
>
> In the newer versions of org, the SCHEDULED string is no longer parsed, and
> I don't see it in agenda, unless I reformat it like this:
>
> * TODO Item
> SCHEDULED: <2018-06-19 Tue>
> some-text
> some-more-text
>
> This broke the habit that I was using for years and also broke my existing
> notes as I'm no longer able to see them in agenda. I wonder if this
> behavior can be changed to work like before.
No it cannot. SCHEDULED and DEADLINE must be in the line right below the
heading. M-x org-lint will help you finding problematic lines.
Not this is not really a change: most code in Org expected such lines to
be located right below the heading since day 1. The agenda was a bit
tolerant on that part. This is particularly important to make Org find
information quickly.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-06-19 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 14:37 In org-mode 9 "Scheduled" and "Deadline" are no longer parsed if they are not in the beginning Igor Katson
2018-06-19 14:44 ` Nicolas Goaziou [this message]
2018-06-19 18:13 ` Ken Mankoff
2018-06-19 18:59 ` Igor Katson
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=87muvqesyp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=igor.katson@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.