From: jca+org@wxcvbn.org (Jérémie Courrèges-Anglas)
To: emacs-orgmode@gnu.org
Subject: [PATCH] Re: Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]
Date: Tue, 10 Apr 2012 14:13:20 +0200 [thread overview]
Message-ID: <87vcl7okdb.fsf_-_@moo.wxcvbn.org> (raw)
In-Reply-To: <871uo1l37g.fsf@gnu.org> (Bastien's message of "Fri, 06 Apr 2012 09:38:43 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 502 bytes --]
Bastien <bzg@gnu.org> writes:
[snip]
> See this footnote in the section "8.3.1 Inserting deadlines or
> schedules" of the manual:
>
> (1) The `SCHEDULED' and `DEADLINE' dates are inserted on the line
> right below the headline. Don't put any text between this line and the
> headline.
Hi. Then I guess the example in "8.3 Deadlines and scheduling" should be
amended. Patch attached.
--
Jérémie Courrèges-Anglas
Empreinte GPG : 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: Deadlines and scheduling documentation patch --]
[-- Type: text/x-patch, Size: 1078 bytes --]
From 0644fc9f9eabc536348841550900a74f4bb5a5e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9mie=20Courr=C3=A8ges-Anglas?= <jca@wxcvbn.org>
Date: Tue, 10 Apr 2012 14:10:03 +0200
Subject: [PATCH] Deadlines and scheduling: Fix order in DEADLINE example
* doc/org.texi (Deadlines and scheduling): fix example, the DEADLINE item
should come right after the headline.
Maybe should the footnote (in 8.3.1) documenting this requirement should come
right into the 8.3 section, after the example?
---
doc/org.texi | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 0be6e2b..f0f6e9d 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5721,8 +5721,8 @@ until the entry is marked DONE. An example:
@example
*** TODO write article about the Earth for the Guide
- The editor in charge is [[bbdb:Ford Prefect]]
DEADLINE: <2004-02-29 Sun>
+ The editor in charge is [[bbdb:Ford Prefect]]
@end example
You can specify a different lead time for warnings for a specific
--
1.7.6
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2012-04-10 12:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 14:41 Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Dave Abrahams
2012-04-06 7:38 ` Bastien
2012-04-06 12:18 ` Dave Abrahams
2012-04-09 11:01 ` Bastien
2012-04-09 11:20 ` Dave Abrahams
2012-04-09 12:49 ` Bastien
2012-04-09 13:58 ` Dave Abrahams
2012-04-09 14:51 ` Bastien
2012-04-09 14:54 ` Dave Abrahams
2012-04-09 15:05 ` Bastien
2012-04-09 15:52 ` Dave Abrahams
2012-04-10 13:43 ` Rainer Stengele
2012-04-10 14:12 ` Bastien
2012-04-09 20:24 ` John Wiegley
2012-04-10 12:13 ` Jérémie Courrèges-Anglas [this message]
2012-04-10 12:34 ` [PATCH] " Bastien
2012-04-10 13:34 ` Jérémie Courrèges-Anglas
2012-04-10 13:40 ` Bastien
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=87vcl7okdb.fsf_-_@moo.wxcvbn.org \
--to=jca+org@wxcvbn.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
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).