From: Ihor Radchenko <yantar92@gmail.com>
To: Ypo <ypuntot@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-timer-start doesn't seem to take the timer string at point [9.5.5 (release_9.5.5 @ z:/emacs-i686/share/emacs/28.2/lisp/org/)]
Date: Thu, 06 Oct 2022 11:43:10 +0800 [thread overview]
Message-ID: <87wn9d62i9.fsf@localhost> (raw)
In-Reply-To: <27db728a-0775-0657-01be-93eb23bef7f2@gmail.com>
Ypo <ypuntot@gmail.com> writes:
> Sorry for my delayed answer. But I don't see it either :/
>
> "The prompt will default to a timer string at
> + point (if any),"
>
> I can't see it well related to the C-u prefix. For example why the "(if
> any)"? It should be unnecessary, since it is the previous explained
> general case.
I feel that you missed the context by reading only the diff in the commit.
The full text in the manual after applying the patch reads like:
- {{{kbd(C-c C-x 0)}}} (~org-timer-start~) ::
#+kindex: C-c C-x 0
#+findex: org-timer-start
Start or reset the relative timer. By default, the timer is set
to 0. When called with a {{{kbd(C-u)}}} prefix, prompt the user for
a starting offset. The prompt will default to a timer string at
point (if any), providing a convenient way to restart taking notes
after a break in the process. When called with a double prefix
argument {{{kbd(C-u C-u)}}}, change all timer strings in the active
region by a certain amount. This can be used to fix timer strings
if the timer was not started at exactly the right moment.
--
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-06 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 12:27 [BUG] org-timer-start doesn't seem to take the timer string at point [9.5.5 (release_9.5.5 @ z:/emacs-i686/share/emacs/28.2/lisp/org/)] Ypo
2022-10-02 13:37 ` Ihor Radchenko
2022-10-02 13:42 ` Ypo
2022-10-03 2:57 ` Ihor Radchenko
2022-10-05 11:23 ` Ypo
2022-10-06 3:43 ` Ihor Radchenko [this message]
2022-10-21 5:36 ` 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=87wn9d62i9.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ypuntot@gmail.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).