From: "Varnit Suri" <vsuri@Brocade.COM> To: Bernt Hansen <email@example.com> Cc: firstname.lastname@example.org Subject: RE: Help with binding new key to change task state Date: Sun, 15 Feb 2009 21:09:18 -0800 [thread overview] Message-ID: <57AC2FA1761300418C7AB8F3EA493C97028221AE@HQ-EXCH-5.corp.brocade.com> (raw) In-Reply-To: <email@example.com> Thanks for your reply. The first trick worked fine. For the second problem though, I 'd not like to cycle through the states. That's coz each time I change the state, I have to log it. So I am trying to define a single key that lets me jump straight to the DONE state (from any other state). C-c C-t C-c works okay coz the last 'c' chooses the DONE state from the menu. Any ideas how I can define a simpler key for this? Thanks. V. -----Original Message----- From: Bernt Hansen [mailto:firstname.lastname@example.org] Sent: Sunday, February 15, 2009 6:52 PM To: Varnit Suri Cc: email@example.com Subject: Re: Help with binding new key to change task state "Varnit Suri" <vsuri@Brocade.COM> writes: > The org manual talks about using C-u C-c C-t to change the state of a > task. This command nicely throws up a list of several intermediate > states to choose from. In addition, I have logging turned on, so each > time I do this, I can log a note about the state change. > > I am merely trying to bind this to a simpler set of keys. I know C-c C-t > is bound to org-todo, but can't figure out what C-u C-c C-t binds to > (describe-key stops at C-u). Or then, maybe I don't know Emacs/Org well > enough yet. Any suggestions? C-c C-t and C-u C-c C-t both bind to the same function. The C-u just provides a prefix value of 4 to the function so it can behave differently (displaying the menu of todo choices) You probably want to set (setq org-use-fast-todo-selection t) so that C-c C-t shows the menu by default. > > The second thing I am trying to do is have a shortcut to take a task > from TODO to DONE without going through the above process. If you have your todo states defined in sequences you can use S-left arrow and S-right arrow to cycle between the states quickly. I use the following TODO settings: (setq org-todo-keywords '((sequence "TODO(t)" "STARTED(s!)" "|" "DONE(d!/!)") (sequence "WAITING(w@/!)" "SOMEDAY(s)" "|" "CANCELLED(c@/!)") (sequence "QUOTATION(q!)" "QUOTED(Q!)" "|" "APPROVED(A@)" "EXPIRED(E@)" "REJECTED(R@)") (sequence "OPENPO(O!)" "|" "CLOSEDPO(C@)") (sequence "|" "NOTE(n)" "PHONE(T)"))) so if I have a task * TODO Do something then S-right arrow moves to STARTED and a second time moves to DONE HTH, Bernt
next prev parent reply other threads:[~2009-02-16 5:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-16 0:00 Varnit Suri 2009-02-16 2:52 ` Bernt Hansen 2009-02-16 5:09 ` Varnit Suri [this message] 2009-02-16 15:33 ` Bernt Hansen 2009-02-17 20:11 ` Varnit Suri 2009-02-16 18:57 ` Ian Barton
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=57AC2FA1761300418C7AB8F3EA493C97028221AE@HQ-EXCH-5.corp.brocade.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='RE: Help with binding new key to change task state' \ /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
Code repositories for project(s) associated with this 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).