From: Carsten Dominik <dominik@science.uva.nl>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: log on state change
Date: Wed, 5 Sep 2007 05:28:44 +0200 [thread overview]
Message-ID: <1f25e5b70c38b0cc9749626500e92846@science.uva.nl> (raw)
In-Reply-To: <m23axvv7y1.fsf@cam.ac.uk>
On Sep 3, 2007, at 21:56, Leo wrote:
> On 2007-09-03 19:32 +0100, Carsten Dominik wrote:
>>>> Yes, since 5.07, you can mis-use the TAGS interface to directly
>>>> switch to TODO states. Check the release notes.
>>>
>>> Is this temporary until a better solution is found?
>>
>> Not at all, I really cannot think of a better solution.
>> The only thing preliminary about this would be the setup
>> using Emacs Lisp. I guess the in-buffer setup like
>>
>> #+SEQ_TODO: TODO(t)....
>>
>> is nice and similar to TAGS, so that will stay.
>
> Using tags to setup todo looks unclean to me. However it is very nice
> to
> be able to set up todo using an interface similar to tags.
Yes, it is not very clean, agreed. Even if you *could* view TODO
keywords as special, privileged tag.
> And since the argument to org-todo has become completely useless
> because
> of this feature. I propose the following:
>
> C-c C-t (`org-todo') brings up an interface similar to the one for
> org-set-tags but only for todos (C-c C-c only for tags)
Hm, yes, this might indeed be cleaner.
> C-u C-c C-t cycle through todo states i.e. the old behavior.
And don't forget that we also have S-right doing cycling.
>
> make an user option to swap C-c C-t and C-u C-c C-t i.e. C-c C-t
> cycle through todo states
>
> automatically shortcut for todos:
> - if it is specified by user then use it
> - otherwise, use the first letter of the name of the todos
> - if the first letter has been taken, use the subsequent
> letter
> - continue until a unique letter is found
That mechanism already exists for tags, easy to re-use it.
> For example,
>
> When `C-c C-t', a buffer shows up:
>
> -*- buffer -*-
>
> => (T)odo (W)aiting (D)elegated
> (C)ancelled (M)aybe (D)one
>
> -*- buffer -*-
>
> 'C-n' and 'C-p' can move to the next/previous todo state
>
> The arrow indicates the current state.
I don't think it is even necessary, to mark the current state.
This is important for tags because of inheritance, and because you
can change several tags with a single call to C-c C-c. For for a single
TODO state change?
>
> Only shortcut in the row indicated by the 'arrow' is in effect thus
> allows (D)one to (D)elegated to co-exist.
Well, I think allowing the same letter to mean different things will
be confusing and will make this special interface less effective.
> Some of the points might be also helpful for tags.
I can't really see which ones, the TAG interface does all this.
- Carsten
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
next prev parent reply other threads:[~2007-09-05 3:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 7:46 log on state change Cezar
2007-09-03 16:25 ` Carsten Dominik
2007-09-03 17:34 ` Leo
2007-09-04 1:00 ` Xavier Maillard
2007-09-03 17:35 ` Leo
2007-09-03 18:32 ` Carsten Dominik
2007-09-03 19:56 ` Leo
2007-09-04 16:43 ` Bastien
2007-09-05 3:32 ` Carsten Dominik
2007-09-05 5:06 ` Bastien
2007-09-05 15:16 ` Leo
2007-09-05 3:28 ` Carsten Dominik [this message]
2007-09-05 10:06 ` Leo
2007-09-05 10:23 ` Carsten Dominik
2007-09-05 15:23 ` Leo
2007-09-05 15:43 ` Carsten Dominik
2007-09-05 20:13 ` Leo
2007-09-05 21:43 ` Carsten Dominik
2007-09-05 22:00 ` Leo
2007-09-05 15:21 ` Leo
2007-09-04 1:00 ` Xavier Maillard
2007-09-14 15:56 ` Carsten Dominik
2007-09-14 17:56 ` Bernt Hansen
2007-09-14 19:38 ` Carsten Dominik
2007-09-14 19:44 ` Bernt Hansen
2007-09-16 10:03 ` Cezar
2007-09-16 12:31 ` Bastien
2007-09-16 18:08 ` Cezar
2007-09-16 21:53 ` Bastien
2007-09-17 17:04 ` Carsten Dominik
2007-09-18 1:00 ` Xavier Maillard
2007-09-21 13:16 ` Bernt Hansen
2007-09-18 1:00 ` Xavier Maillard
2007-09-18 1:00 ` Xavier Maillard
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=1f25e5b70c38b0cc9749626500e92846@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@gmail.com \
/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).