emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Somelauw ." <somelauw@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why is there no org-agenda-todo-next-keyword function?
Date: Mon, 6 Nov 2017 21:30:27 +0100	[thread overview]
Message-ID: <CA+gt_a8Ck4tPf4gTEuFt+KyQugCQpseJaeWLFz2dR1Ld2Fo+oQ@mail.gmail.com> (raw)
In-Reply-To: <87h8u7jz2h.fsf@nicolasgoaziou.fr>

2017-11-06 14:50 GMT+01:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Hello,
>
> "Somelauw ." <somelauw@gmail.com> writes:
>
>> In an org-agenda buffer the following functions are defined and bound:
>> - org-agenda-todo-nextset (C-S-left)
>> - org-agenda-todo-previousset (C-S-right)
>> which change between sets of todo keywords.
>>
>> Yet the following corresponding functions are missing:
>> - org-agenda-todo-next-keyword
>> - org-agenda-todo-previous-keyword
>> which should (if implemented) change between individual todo keywords.
>>
>> That means that If I have the following setup:
>>
>> ```emacs-lisp
>>   (setq org-todo-keywords
>>         '((sequence "TODO(t)" "|" "DONE(d)")
>>           (sequence "NEXT(n)" "|" "WAITING(w)")))
>> ```
>>
>> There is no way to change a task to DONE using C-S-left and C-S-right
>> bindings alone.
>>
>> What's the reason that these functions are missing?
>
> This is not an answer, which would not be very useful anyways, to your
> question, but have you tried `org-agenda-todo', i.e. `t' on an entry?
>
> Regards,
>
> --
> Nicolas Goaziou

Thanks for your response. I already knew about `t`.
I was just wondering whether there is a good reason for this
inconsistency or if this should be changed.

Kind regards,
Somelauw

next prev parent reply	other threads:[~2017-11-06 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 21:49 Why is there no org-agenda-todo-next-keyword function? Somelauw .
2017-11-06 13:50 ` Nicolas Goaziou
2017-11-06 20:30   ` Somelauw . [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-04 13:11 Somelauw .

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=CA+gt_a8Ck4tPf4gTEuFt+KyQugCQpseJaeWLFz2dR1Ld2Fo+oQ@mail.gmail.com \
    --to=somelauw@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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 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).