From: Robert Nikander <robert.nikander@icloud.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
Date: Wed, 8 Feb 2023 09:11:16 -0500 [thread overview]
Message-ID: <830BAEAD-AA4C-4226-A93E-1329B41194D7@icloud.com> (raw)
In-Reply-To: <C9F1FC5B-81DC-47B2-9359-3F191399F1B5@icloud.com>
> On Feb 8, 2023, at 5:14 AM, Ihor Radchenko <yantar92@posteo.net> wrote:
>
> Robert Nikander <robert.nikander@icloud.com> writes:
>
>> […]
>>
>> If I put point on the minutes of 12:30 (second line) and hit S-M-<UP>, it moves the time to 12:35, but nothing else moves. Based on the docs, I thought it would shift one of the other lines.
>
> S-M-<UP> only considers clock history during current Emacs session. Will
> clarifying this in the manual suffice for your use-case?
>
> If not limiting the command to current clock history, we would need to
> look across every single Org file searching for intersecting clocks -
> extremely resource-intensive procedure.
>
> Note that you can use agenda clock check to catch clock inaccuracies.
I’m pretty much a beginner with the clock features, so I don’t have an opinion yet on how it should work. But yes, it seems like clarifying the manual there would be an improvement.
I don’t know what agenda clock check is. Is that a certain function, or agenda view? Searching the manual and functions for that term didn’t yield anything obvious.
next prev parent reply other threads:[~2023-02-08 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 21:46 [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5] Robert Nikander
2023-02-08 10:14 ` Ihor Radchenko
[not found] ` <C9F1FC5B-81DC-47B2-9359-3F191399F1B5@icloud.com>
2023-02-08 14:11 ` Robert Nikander [this message]
2023-02-08 19:51 ` Mark Barton
2023-02-09 9:58 ` 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=830BAEAD-AA4C-4226-A93E-1329B41194D7@icloud.com \
--to=robert.nikander@icloud.com \
--cc=emacs-orgmode@gnu.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).