Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-06 Thread Carsten Dominik
On Oct 5, 2007, at 22:34, John Wiegley wrote: Carsten Dominik [EMAIL PROTECTED] writes: I think using LOGGING is a bit better. So what do I do? More votes? If you want to start using the facility for generally overriding Lisp values, then your original proposal is better. But if this

Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-05 Thread Carsten Dominik
On Oct 4, 2007, at 13:24, Bastien wrote: Carsten Dominik [EMAIL PROTECTED] 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

Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-05 Thread John Wiegley
Carsten Dominik [EMAIL PROTECTED] writes: I think using LOGGING is a bit better. So what do I do? More votes? If you want to start using the facility for generally overriding Lisp values, then your original proposal is better. But if this is just going to be for a few exceptions, LOGGING

Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-04 Thread Carsten Dominik
On Oct 3, 2007, at 19:57, John Wiegley wrote: Carsten Dominik [EMAIL PROTECTED] writes: OK, how about a general mechanism like this: If there is a property :org-log-done:, it will be used instead of the current value of org-log-done during TODO state changeing, like * repetitive entry

Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-04 Thread Bastien
Carsten Dominik [EMAIL PROTECTED] 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

Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-03 Thread Carsten Dominik
On Sep 29, 2007, at 5:50, John Wiegley wrote: I love using #+STARTUP: lognotestate for noting down when and why a task changes state. However, I have several tasks which recur daily, or once every two days. The size of these tasks is starting to get crazy, since there are empty DONE

Re: [Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-10-03 Thread John Wiegley
Carsten Dominik [EMAIL PROTECTED] writes: OK, how about a general mechanism like this: If there is a property :org-log-done:, it will be used instead of the current value of org-log-done during TODO state changeing, like * repetitive entry :PROPERTIES: :org-log-done: nil :END:

[Orgmode] FR: Using properties to customize global settings on a per-entry basis

2007-09-28 Thread John Wiegley
I love using #+STARTUP: lognotestate for noting down when and why a task changes state. However, I have several tasks which recur daily, or once every two days. The size of these tasks is starting to get crazy, since there are empty DONE messages continually accruing. I'd like either a) an