From: Bastien <bzg@altern.org>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: "[emacs-orgmode] list" <emacs-orgmode@gnu.org>
Subject: Re: Release 5.23a - [BUG ?] closing-notes
Date: Tue, 11 Mar 2008 18:23:02 +0000 [thread overview]
Message-ID: <87od9lw261.fsf@bzg.ath.cx> (raw)
In-Reply-To: <241642.11229.qm@web28315.mail.ukl.yahoo.com> (Giovanni Ridolfi's message of "Tue, 11 Mar 2008 17:58:18 +0100 (CET)")
Hi Giovanni,
Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> writes:
> #+SEQ_TODO: TODO DONE
> #+STARTUP: lognotedone
>
> * TODO write data proof
> DEADLINE: <2008-03-10 lun +1d>
Use lognoterepeat for logging such timestamps.
> Comment: With v.5.21 I had:
> - CLOSING NOTE [2008-03-10 lun 16:43]
>
> with v. 5.23(a?) a string is added to the file:
>
> -----------------------------------------
> - State "DONE" [2008-03-11 mar 17:30]
Yes, see the option `org-log-note-headings' in case you want to
configure this.
> This seems to be not coherent with the manual
> that states:
>
> |-
> |"a line `CLOSED: [timestamp]' will be inserted just
> |after the headline."
> |-
AFAIU the CLOSED: [timestamp] is added after the headline when closing
non-repeating timestamps. Adding such a cookie would actually be a bit
weird for _repeating_ timestamps...
Hope this helps,
--
Bastien
next prev parent reply other threads:[~2008-03-11 18:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 22:04 Release 5.23a Carsten Dominik
2008-03-11 0:03 ` Xin Shi
2008-03-11 0:20 ` Bastien
2008-03-11 0:57 ` Xin Shi
2008-03-11 1:15 ` Bastien Guerry
2008-03-11 1:52 ` Xiao-Yong Jin
2008-03-11 2:21 ` Xin Shi
2008-03-11 2:05 ` Xin Shi
2008-03-11 2:56 ` Carsten Dominik
2008-03-11 3:47 ` Richard G Riley
2008-03-11 5:11 ` Carsten Dominik
2008-03-11 13:26 ` Xin Shi
2008-03-11 15:00 ` Richard G Riley
2008-03-11 15:03 ` Xin Shi
2008-03-13 7:16 ` Carsten Dominik
2008-03-11 16:58 ` Release 5.23a - [BUG ?] closing-notes Giovanni Ridolfi
2008-03-11 18:23 ` Bastien [this message]
2008-03-12 21:14 ` Release 5.23a Jost Burkardt
2008-03-13 7:36 ` Carsten Dominik
2008-03-13 16:34 ` Carsten Dominik
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=87od9lw261.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=giovanni.ridolfi@yahoo.it \
/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).