emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eddward DeVilla" <eddward@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org, Leo <sdl.web@gmail.com>
Subject: Re: Re: Org-mode 4.69
Date: Wed, 21 Mar 2007 10:07:33 -0500	[thread overview]
Message-ID: <b71b18520703210807qbca007ei6add3b76c651a1af@mail.gmail.com> (raw)
In-Reply-To: <1e1d92fc98145e6b53ca8593e3b4bc3f@science.uva.nl>

    It looks like there might some more discussion here, but I'd like
to chime in and say I kinda like what you have done with the multiple
sequences.  Of course, I'm not using some of the more advanced
features such as logging state changes.  For my simple use of TODO
items, this is pretty nice.

    The way I see it, I can have a sequence for simple todos, one for
fuller projects, one for wishlist/investigation/bug-report items and
so on.  I'd use C-S-arrow to set the sequence type. S-arrow as usual
while working and (possibly) C-S-arrow to promote say a wish-list item
into a project.  Heck, could I even have a single state sequence
CANCEL for the missing not-done done state?

Edd

On 3/21/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>
> On Mar 21, 2007, at 11:21, Leo wrote:
> > I feel this too complicated.
>
> First, I don't think it is complicated at all, try it out.
>
> I have already gotten used to it:
> C-S-right to select the right sequence initially.  After that,
> everything works exactly as before.  My description sounds
> complicated because I listed all the commands that are can be
> used, but you really only need these two.
>
> > Isn't it more intuitive and consistent to
> > make this work like #+CATEGORY and #+ARCHIVE?
>
> To be honest, I don't think this makes sense in this case,
> my suspicion is that you would get many more #+SEQ_TODO
> lines in a real-life buffer than #+CATEGORY lines.
> So I think this solution is much more general and
> workable.  Lets see what other people have to say about it.
>
> Thanks for the feedback.
>
>   - Carsten
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

  parent reply	other threads:[~2007-03-21 15:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21  9:00 Org-mode 4.69 Carsten Dominik
2007-03-21 10:21 ` Leo
2007-03-21 10:36   ` Carsten Dominik
2007-03-21 14:27     ` Jason F. McBrayer
2007-03-21 15:11       ` Carsten Dominik
2007-03-21 22:21         ` Carsten Dominik
2007-03-21 23:28           ` Jason F. McBrayer
2007-03-22 13:59             ` Carsten Dominik
2007-03-22 15:21               ` Jason F. McBrayer
2007-03-22 15:50                 ` Carsten Dominik
2007-03-22 16:45                   ` Jason F. McBrayer
2007-03-26 16:29                     ` Carsten Dominik
2007-03-21 15:07     ` Eddward DeVilla [this message]
2007-03-21 15:18   ` Eddward DeVilla

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=b71b18520703210807qbca007ei6add3b76c651a1af@mail.gmail.com \
    --to=eddward@gmail.com \
    --cc=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).