Bernt Hansen wrote:
<reordered (and wrapped) the email to remove top-posting>
Keith Swartz <g...@oneroad.com> writes:
Carsten Dominik wrote:
On May 26, 2009, at 10:23 AM, Manish wrote:
On Sat, May 23, 2009 at 4:45 AM, Keith Swartz wrote:
However, if I use M-S-ENTER to combine the above two steps into
one (create
a "TODO" item), it does NOT create an entry in the LOGBOOK for State
"TODO" from "" at all. Is that a bug?
IMO, this is not really a state change.
In interesting point, and something up for discussion.
I personally am neter interesting in recording a time stamp when
first switching an item to TODO. Furthermore, for other state
changes I prefer to record a note.
However, M-S-RET is really meant for fast adding of one or more TODO
entries, and being prompted for a state change note would be really
annoying here.
Up for discussion, I am willing to install a variable here....
I can see where M-S-ENTER prompting for a status note change would be
annoying. Personally, I don't use that feature, so I didn't think of
that -- I'm more interested in the timestamps. Basically, I like being
able to record /when/ something was first entered as a todo item --
gives me a good way to see which items are the oldest.
One thought is to record the state change, but default the status note
to "TODO created", rather than prompting for it.
Then again, maybe a variable is the best answer here, because sooner
or later, somebody is going to want to change that. Normally, I'd hate
to add more and more variables just to complicate things, but org-mode
seems to have no shortage of them. (That's a good thing!) :)
I use org-remember for creating tasks where I want to know the created
time. I create most of my tasks with the remember interface and it's
easy to put the date in the template with %u.
For me every log entry creates a log drawer and I wouldn't want that by
default for every new task created with M-S-RET.
http://doc.norang.ca/org-mode.html#Remember
Actually, that's a good idea. I just went and modified my remember
template to emulate the logbook behavior, so now I can use that
consistently. Should have thought of that.
But we still have an inconsistency here. There seems to be a rather
widespread agreement that creating a TODO item shouldn't register a
state change. If there's no objection to that (and there isn't from
me), then changing a regular bullet to the "TODO" state for the first
time shouldn't either. So I think that's kind of a bug.
I don't think it's worth having a variable to turn it on/off, imho,
since there are other ways to achieve this, but if we want to preserve
that functionality for backwards compatibility for a few releases, I'd
think it's not much work to add one.
Thanks for the great ideas.
Keith
|
