From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: FR: Using properties to customize global settings on a per-entry basis
Date: Thu, 04 Oct 2007 12:24:33 +0100 [thread overview]
Message-ID: <87fy0ri1dq.fsf@bzg.ath.cx> (raw)
In-Reply-To: <f593b5c12d3ab522944380546c816ce3@science.uva.nl> (Carsten Dominik's message of "Thu, 4 Oct 2007 09:26:27 +0200")
Carsten Dominik <dominik@science.uva.nl> writes:
>>> * repetitive entry
>>> :PROPERTIES:
>>> :org-log-done: nil
>>> :END:
>>
>> Sounds like a great way to do it!
>
> The alternative would be a LOGGING property where you could set the same
> keywords as in the STARTUP line. What is better?
I think using LOGGING is a bit better.
BTW, this is documented in (info "(Org)In-buffer settings") :
| logging | record a timestamp when an item is marked DONE |
| nologging | don't record when items are marked DONE |
| lognotedone | record timestamp and a note when DONE |
| lognotestate | record timestamp and a note when TODO state changes |
| logrepeat | record a note when re-instating a repeating item |
| nologrepeat | do not record when re-instating repeating item |
| lognoteclock-out | record timestamp and a note when clocking out |
But the docstring of `org-log-done' doesn't mention all these options.
And (info "(Org)Progress Logging") should mention all these option
somewhere, or at least link back to the in-buffer settings back.
--
Bastien
next prev parent reply other threads:[~2007-10-04 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 3:50 FR: Using properties to customize global settings on a per-entry basis John Wiegley
2007-10-03 13:27 ` Carsten Dominik
2007-10-03 17:57 ` John Wiegley
2007-10-04 7:26 ` Carsten Dominik
2007-10-04 11:24 ` Bastien [this message]
2007-10-05 8:02 ` Carsten Dominik
2007-10-05 12:13 ` Bastien
2007-10-05 12:28 ` Rainer Stengele
2007-10-05 20:34 ` John Wiegley
2007-10-06 3:06 ` bzg
2007-10-06 6:52 ` 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=87fy0ri1dq.fsf@bzg.ath.cx \
--to=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).