emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Richard G Riley <rileyrgdev@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Categories
Date: Sun, 14 Oct 2007 08:14:04 +0200	[thread overview]
Message-ID: <c26ab44835d70ad8b3537c5c2b7ba783@science.uva.nl> (raw)
In-Reply-To: <fgodf3dx0v.fsf@home.net>


On Oct 13, 2007, at 14:22, Richard G Riley wrote:

> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> On Oct 12, 2007, at 19:20, Richard G Riley wrote:
>>> I have a possible bug here (5.12). When embedding the CATEGORY as a
>>> property e.g in my org file
>>
>> Yes, logging state changes is broken in 5.12, *#$&*&#&$.
>>
>> Fixed in 5.12c, thanks.
>>
>>> ,----
>>> |  '(org-agenda-custom-commands
>>> |    (quote (
>>> | 	   ("d" org-todo "DELEGATED" nil)
>>> |            ("c" org-todo "DONE|DEFERRED|CANCELLED" nil)
>>> |            ("w" org-todo "WAITING" nil)
>>> | 	   ("W" agenda ""
>>> `----
>
> I took this from a tutorial out there in google land.
>
>>
>>
>> What an innovative way of totally misusing org-agenda-custom-commands.
>> `C-c a d' will indeed change a TODO state, something
>> org-agenda-custom-commands
>> was not designed for (and which I do not recommend...)!
>>
>> But "c" will not work, the symbol for creating a TODO list is
>> `alltodo', not `org-todo'.
>
> I'm not sure I understand, but I will remove this regardless. Why are
> you mentioning creating a TODO list?

All the commands in org-agenda-custom-commands are intended to
create some kind of list, either an agenda view, or a sparse tree.
But, since in the end they call a function, someone has used this
to create commands to directly jump to a state.

>  The commands above are "jumpt to
> state commands - not create commands. So, if the code I cribbed above 
> is
> not correct, how is the best way to add commands to agenda mode - its
> not obvious how to jump straight to a state as opposed to cycling to it
> manually with all the note prompts that come with that flow.

The recommended way is to set up keys for the TODO keywords like this:

#+SEQ_TODO: TODO(t) WAITING(w) | DONE(d)

(you can also do this in lisp customization)

If you then call C-c C-t with a prefix arg (i.e. C-c C-c C-t)
you can directly jump to any state.  If you like that a lot,
you can even get this interface without the prefix argument, by
setting the variable org-use-fast-todo-selection to t.

- Carsten

      reply	other threads:[~2007-10-14  6:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 23:05 Categories Richard G Riley
2007-10-12  3:16 ` Categories Eddward DeVilla
2007-10-12  9:00   ` Categories Richard G Riley
2007-10-12 13:31     ` Categories Bastien
     [not found]       ` <fgy7e85vf3.fsf@home.net>
2007-10-12 14:56         ` Categories Bastien
2007-10-12 14:12           ` Categories Richard G Riley
2007-10-12 14:27             ` Categories Carsten Dominik
2007-10-12 15:04               ` Categories Richard G Riley
2007-10-12 17:00                 ` Categories Bastien
     [not found]                   ` <qfr6k0b8f8.fsf@home.net>
     [not found]                     ` <87bqb4uri3.fsf@bzg.ath.cx>
     [not found]                       ` <ml641cb5wj.fsf@home.net>
     [not found]                         ` <87r6k0tboe.fsf@bzg.ath.cx>
     [not found]                           ` <0sprzk9pcu.fsf@home.net>
     [not found]                             ` <87641cdniz.fsf@bzg.ath.cx>
     [not found]                               ` <uzk5prdwxm.fsf@home.net>
     [not found]                                 ` <87tzovjeer.fsf@bzg.ath.cx>
     [not found]                                   ` <13k5prcg2a.fsf@home.net>
     [not found]                                     ` <87bqb3jcsm.fsf@bzg.ath.cx>
     [not found]                                       ` <77zlykith7.fsf@home.net>
2007-10-15 11:32                                         ` Categories Bastien
     [not found]                   ` <jnr6jwtk1o.fsf@home.net>
2007-10-15 17:54                     ` Categories Bastien
     [not found]                       ` <t1lka4thoz.fsf@home.net>
2007-10-15 18:38                         ` Categories Bastien
     [not found]                           ` <jbhcksjmnx.fsf@home.net>
2007-10-15 18:57                             ` Categories Bastien
     [not found]                               ` <2yd4vgdyxe.fsf@home.net>
2007-10-15 19:24                                 ` Categories Bastien
2007-10-12 17:07                 ` Categories Carsten Dominik
2007-10-12 17:20                   ` Categories Richard G Riley
2007-10-12 18:20                     ` Categories Carsten Dominik
2007-10-13 12:22                       ` Categories Richard G Riley
2007-10-14  6:14                         ` Carsten Dominik [this message]

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=c26ab44835d70ad8b3537c5c2b7ba783@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.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).