emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Tyree <alantyree@gmail.com>
To: Alan L Tyree <alantyree@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: DEADLINE: position in entry
Date: Thu, 10 Nov 2016 10:44:52 +1100	[thread overview]
Message-ID: <CAGMsgMw0toyDQUwFjoWa6iOgOsfgO8AjhzDRb3ReMz5ymuSmfQ@mail.gmail.com> (raw)
In-Reply-To: <87eg2ki5tz.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

On 10 November 2016 at 10:36, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Alan L Tyree <alantyree@gmail.com> writes:
>
> > On 10/11/16 05:51, Philip Hudson wrote:
>
> > Also, if this really is the case, then the manual needs to be
> > modified. Under 8.1, it says
> >
> > " A timestamp can appear anywhere in the headline or body of an Org tree
> > entry."
>
> Section 8.1 is about regular time-stamps, which are not necessarily tied
> to DEADLINE and SCHEDULED keyword. Therefore, the sentence above is
> true.
>
> > and under 8.3:
> >
> > "A timestamp may be preceded by special keywords to facilitate planning:"
> >
> > I can't see anywhere that requires the DEADLINE: keyword to be flush
> > against a heading.
>
> This is in 8.3.1, first footnote.
>
> So it is. Not exactly prominent :-). I still think the manual is
misleading, and is there some reason that "planning" items are treated
different from plain old appointment timestamps? I just seems (to a
non-programmer) to be an unnecessary restriction.

Cheers,
Alan


> Regards,
>
> --
> Nicolas Goaziou
>



-- 
Alan L Tyree                    http://austlii.edu.au/~alan
<http://www2.austlii.edu.au/~alan>
Tel:  04 2748 6206            sip:typhoon@iptel.org

[-- Attachment #2: Type: text/html, Size: 2270 bytes --]

  reply	other threads:[~2016-11-09 23:45 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 [this message]
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
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

  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=CAGMsgMw0toyDQUwFjoWa6iOgOsfgO8AjhzDRb3ReMz5ymuSmfQ@mail.gmail.com \
    --to=alantyree@gmail.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 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).