From: Nick Dokos <nicholas.dokos@hp.com>
To: Arun Persaud <apersaud@lbl.gov>
Cc: Bastien <bzg@altern.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: logdone enhancement
Date: Wed, 27 Feb 2013 14:08:09 -0500 [thread overview]
Message-ID: <4042.1361992089@alphaville> (raw)
In-Reply-To: Message from Arun Persaud <apersaud@lbl.gov> of "Wed, 27 Feb 2013 10:39:03 PST." <512E52C7.2050009@lbl.gov>
Arun Persaud <apersaud@lbl.gov> wrote:
> Hi
>
> >> * project
> >> ** TODO headline :repeat:
> >> a longer description of what the todo item is about
> >> SCHEDULED: <2013-06-18 Tue +1m>
> >
> > The SCHEDULED line should be right after the headline, see the manual.
> > It can sometimes work when it is on another line, but this is
> > accidental, you should put the line right after the headline.
>
> I just tried
>
> * project
> ** TODO headline :repeat:
> SCHEDULED: <2013-06-18 Tue +1m>
> a longer description of what the todo item is about
>
> but this will still add the state-changed-line between the SCHEDULED
> line and the longer description (it will also add the property drawer
> there, if it doesn't exist). If you track some daily changes this can
> move the longer description away from the top quite fast, which is what
> I would like to avoid.
>
Isn't that what the LOGBOOK drawer is for? You put the mess in there, so
it's available when you open it, but you don't have to look at it most of
the time.
Nick
next prev parent reply other threads:[~2013-02-27 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 6:21 logdone enhancement Arun Persaud
2013-02-27 8:33 ` Bastien
2013-02-27 9:15 ` Sebastien Vauban
2013-02-27 9:25 ` Bastien
2013-02-27 10:04 ` Sebastien Vauban
2013-02-27 12:22 ` Bastien
2013-02-27 18:39 ` Arun Persaud
2013-02-27 19:08 ` Nick Dokos [this message]
2013-02-27 20:09 ` Arun Persaud
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=4042.1361992089@alphaville \
--to=nicholas.dokos@hp.com \
--cc=apersaud@lbl.gov \
--cc=bzg@altern.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).