From: Yasushi SHOJI <yashi@atmark-techno.com>
To: emacs-orgmode@gnu.org
Subject: Re: DEADLINE: position in entry
Date: Mon, 21 Nov 2016 14:10:52 +0900 [thread overview]
Message-ID: <8737ilifj7.wl@dns1.atmark-techno.com> (raw)
In-Reply-To: <CAGMsgMzk17a4=fnn3xGmbFCM+qTSwO++i0CQJkyj61G=jfaEPw@mail.gmail.com>
On Wed, 09 Nov 2016 18:37:00 +0900,
Alan Tyree wrote:
>
> Is this the way it should be? The first DEADLINE: shows up both as a
> warning and on the due date in the agenda, but the second one does
> not. It only works for me if the DEADLINE: is the first line after the
> heading. Version 9, emacs 24
>
> *** test 1
> DEADLINE: <2016-11-19 Sat>
>
> *** test 2
>
> DEADLINE: <2016-11-19 Sat>
at release_9.0.1-47-gb062593 with the following org file, org-agenda
shows the closed entry. Is this also related?
Yes, org-lint complains about the 4th "scheduled" line saying:
"Misplaced planning info line", but isn't deadline planning info line?
is any of planning info line not allowed in the body?
---- >8 ---- cut ---- >8 ----
* DONE org
DEADLINE: [2016-01-07 Thu 17:39]
SCHEDULED: <2015-09-29 Tue .+1w>
---- >8 ---- cut ---- >8 ----
; /tmp/a.el
(add-to-list 'load-path "~/src/org-mode/lisp")
(setq org-agenda-files '("/tmp/a.org"))
---- >8 ---- cut ---- >8 ----
$ emacs -Q -l /tmp/a.el -f 'org-agenda'
--
yashi
next prev parent reply other threads:[~2016-11-21 5:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 9:37 DEADLINE: position in entry Alan Tyree
2016-11-09 14:20 ` Marco Wahl
2016-11-09 18:51 ` Philip Hudson
2016-11-09 20:42 ` Alan L Tyree
2016-11-09 23:36 ` Nicolas Goaziou
2016-11-09 23:44 ` Alan Tyree
2016-11-09 23:47 ` Samuel Wales
2016-11-09 23:59 ` Alan Tyree
2016-11-10 15:08 ` Nicolas Goaziou
2016-11-10 21:05 ` Alan Tyree
2016-11-11 0:12 ` Nicolas Goaziou
2016-11-11 1:52 ` Alan Tyree
2016-11-09 23:29 ` Nicolas Goaziou
2016-11-21 5:10 ` Yasushi SHOJI [this message]
2016-11-21 18:08 ` Sebastien Vauban
2016-11-23 8:09 ` Yasushi SHOJI
2016-11-25 11:24 ` Nicolas Goaziou
2016-11-29 7:54 ` Yasushi SHOJI
2016-11-29 8:35 ` Nicolas Goaziou
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=8737ilifj7.wl@dns1.atmark-techno.com \
--to=yashi@atmark-techno.com \
--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
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.