From: Ypo <ypuntot@gmail.com>
To: Ihor Radchenko <yantar92@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: Sun, 2 Oct 2022 15:42:03 +0200 [thread overview]
Message-ID: <ae3befcf-1f62-fc84-e63c-16cd45bbaf78@gmail.com> (raw)
In-Reply-To: <87h70mz6q4.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Oh! Thanks
I didn't understand. Maybe this would be more understandable?:
> When called with a ‘C-u’ prefix, prompt the user for a starting
> offset or, if there is a timer string at point, this is taken as the
> default, ...
Or:
> When called with a ‘C-u’ prefix, there are 2 options: prompt the user for a starting
> offset. Or, if there is a timer string at point, this is taken as the
> default, ...
El 02/10/2022 a las 15:37, Ihor Radchenko escribió:
> Ypo<ypuntot@gmail.com> writes:
>
>> In the manual, it says:
>>
>>> C-c C-x 0 (|org-timer-start|)
>>>
>>> ... If there is a timer string at point, this is taken as the
>>> default, providing a convenient way to restart taking notes after
>>> a break in the process...
>>> https://orgmode.org/manual/Timers.html
>>>
>> I am trying it, but the timer starts at 0:00:00
> You missed the previous sentence in the manual.
>
> When called with a ‘C-u’ prefix, prompt the user for a starting
> offset. If there is a timer string at point, this is taken as the
> default, ...
>
> The value at point is only taken into account with prefix argument.
>
[-- Attachment #2: Type: text/html, Size: 2442 bytes --]
next prev parent reply other threads:[~2022-10-02 13: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 [this message]
2022-10-03 2:57 ` Ihor Radchenko
2022-10-05 11:23 ` Ypo
2022-10-06 3:43 ` Ihor Radchenko
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=ae3befcf-1f62-fc84-e63c-16cd45bbaf78@gmail.com \
--to=ypuntot@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).