emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: log on state change
Date: Tue, 04 Sep 2007 18:43:58 +0200	[thread overview]
Message-ID: <87sl5ufkj5.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m23axvv7y1.fsf@cam.ac.uk> (Leo's message of "Mon, 03 Sep 2007 20:56:54 +0100")

Leo <sdl.web@gmail.com> writes:

> 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.
>
> 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)

I wish we could stick to the yes-very-busy C-c C-c key for setting both
TODOs and tags.

Here is another suggestion: why not restrict the fast selection to TODO
keywords when the point is at TODO keywords, and to tags when the point
is on tags?

This would make C-c C-c even more context-aware, but I guess this is
what most users expect from it. And since the current behavior is okay,
I guess this new contextual behavior should be set through an option,
defaulting to nil.

Another argument to let C-c C-t continue its job is that it is able to
distinguish between "sequence" TODOs and "type" TODOs. This is extremely
useful -- especially when C-c C-t is bound to `org-agenda-todo' and you
don't remember whether the expected TODO keywords for a headline are
part of a sequence or are types.

Regards,

-- 
Bastien

  reply	other threads:[~2007-09-04 16:44 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 [this message]
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
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=87sl5ufkj5.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).