emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org
Cc: public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: Re: Selection of TODO entry keyword with S-right arrow
Date: Mon, 17 Nov 2014 10:49:01 +0100	[thread overview]
Message-ID: <86ppcmgnsi.fsf@example.com> (raw)
In-Reply-To: <86ioin49k6.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org> (Sebastien Vauban's message of "Mon, 10 Nov 2014 11:46:49 +0100")



Hello,

Sebastien Vauban wrote:
> Up to recently, with the following customization:
>
>   (setq org-todo-keywords
>         '((sequence "NEW(n!)" "TODO(t!)" "STRT(s!)" "WAIT(w!)" "SDAY(y!)"
>                     "|" "DONE(d!)" "CANX(x!)")
>           (sequence "QTE(q!)" "QTD(Q!)"
>                     "|" "APP(A!)" "REJ(R!)") 
>           (sequence "OPENPO(O!)"
>                     "|" "CLSDPO(C!)")))
>
> To select the TODO state "NEW" or "TODO" for an entry which had no TODO
> keyword, I just had to `S-right' once or twice:
>
> 1. NEW
> 2. TODO
>
> Now, `S-right' does cycle in a new order:
>
> 1. OPENPO
> 2. CLSDPO
> 3. QTE
> 4. QTD
> 5. APP
> 6. REJ
> 7. NEW
> 8. TODO
>
> See http://screencast.com/t/FyECLZ3y.

61a241f0dc07aef5a3a5c2bd037a197236bde2e6 is the first bad commit
commit 61a241f0dc07aef5a3a5c2bd037a197236bde2e6
Author: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Date:   Tue Oct 14 10:53:29 2014 +0200

    Rewrite setup keywords initialization

    * lisp/org-table.el (org-table-set-constants): Remove function.
    * lisp/org.el (org-set-regexps-and-options): Rewrite function.  Merge
      it with `org-set-regexps-and-options-for-tags'.
    (org-set-regexps-and-options-for-tags): Remove function
    (org--setup-collect-keywords, org--setup-process-tags): New functions.
    (org-mode): Remove `org-set-regexps-and-options-for-tags' call.
    (org-agenda-prepare-buffers): Use optimized setup for tags in all
    cases.  Improve docstring.
    (org-make-options-regexp): Make returned regexp more efficient.

:040000 040000 afaa4ae741d1427954081fcbc29ee4a0363e6636 4a2d2634d397a45d3c9528fb1919a6e1a1315430 M      lisp

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2014-11-17  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 10:46 Selection of TODO entry keyword with S-right arrow Sebastien Vauban
     [not found] ` <86ioin49k6.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2014-11-17  9:49   ` Sebastien Vauban [this message]
2014-11-18  8:43     ` Sebastien Vauban

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=86ppcmgnsi.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.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).