From: Ihor Radchenko <yantar92@posteo.net>
To: "Samuel W. Flint" <swflint+orgmode@flintfam.org>
Cc: Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH 2/2] doc/org-manual.org: Document org-clock-{in,out}-switch-to-state
Date: Mon, 24 Oct 2022 09:13:55 +0000 [thread overview]
Message-ID: <87eduxporw.fsf@localhost> (raw)
In-Reply-To: <87r0yzvhi9.fsf@flintfam.org>
"Samuel W. Flint" <swflint+orgmode@flintfam.org> writes:
> + #+vindex: org-clock-in-switch-to-state
> + #+vindex: org-clock-in-next-state
> + #+findex: org-clock-in-next-state-function
> + The variable ~org-clock-in-switch-to-state~ controls if and how a
> + current task's TODO state is changed. No change (a ~nil~) is the
> + default. A specific state may be forced with a string value. The
> + ~org-clock-in-next-state~ alist may be utilized by setting it to
> + ~org-clock-in-next-state-function~, or a custom function may be
> + used. This custom function should take the current state, and
> + return either a new state or ~nil~ to keep the current state.
First of all, thanks for the patch!
However, it is not clear for me what is the purpose of this new feature
(even after reading the proposed patch to the manual).
Could you please explain in simple words when your new feature can be
useful?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-10-24 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 18:29 [PATCH 2/2] doc/org-manual.org: Document org-clock-{in,out}-switch-to-state Samuel W. Flint
2022-10-24 9:13 ` Ihor Radchenko [this message]
2022-10-24 14:14 ` Samuel W. Flint
2022-10-25 7:27 ` Ihor Radchenko
2023-07-16 8:24 ` Ihor Radchenko
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=87eduxporw.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=swflint+orgmode@flintfam.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).