emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Tyree <alantyree@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: DEADLINE: position in entry
Date: Thu, 10 Nov 2016 10:59:49 +1100	[thread overview]
Message-ID: <CAGMsgMwsxYDNo12rNd-xT_17dmwuO2m9FUF6NJVe8C5L-gHDjg@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8sTYVi3i6y1xD1327KjHHokZ+gZMG+bUevYkuj0bfv3EQ@mail.gmail.com>

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

On 10 November 2016 at 10:47, Samuel Wales <samologist@gmail.com> wrote:

> iirc we've discussed whether planning lines (i.e. scheduled, deadline,
> closed at this time) should be flexible.  we concluded to make them
> strict.
>
> check archives for the discussion.  :) everything goes through this
> mailing list.
>
> OK, I'll accept that and have a look at the rationale. However, since
DEADLINE: is so terribly important, I think that there should be a
prominent warning in the manual that they are simply ignored if not
positioned correctly. Warnings should appear, at the very least, in 8.1 and
8.3.

Suggested wording:

In 8.1:


timestamp can appear anywhere in the headline or body of an Org tree
entr UNLESS is is preceded by a keyword in which case it must be properly
positioned or it will be ignored: see 8.3 for details.

In 8.3:

A timestamp may be preceded by special keywords to facilitate planning.
WARNING: both the timestamp and the keyword are ignored if not positioned
immediately following the headline. No space or other text is allowed.

Regards,
Alan


> --
> The Kafka Pandemic: http://thekafkapandemic.blogspot.com
>
> The disease DOES progress.  MANY people have died from it.  And
> ANYBODY can get it.
>
> Denmark: free Karina Hansen NOW.
>   UPDATE 2016-10: home, but not fully free
>



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

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

  reply	other threads:[~2016-11-09 23:59 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 [this message]
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=CAGMsgMwsxYDNo12rNd-xT_17dmwuO2m9FUF6NJVe8C5L-gHDjg@mail.gmail.com \
    --to=alantyree@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@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 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).