emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Robert Nikander <robert.nikander@icloud.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
Date: Wed, 08 Feb 2023 10:14:25 +0000	[thread overview]
Message-ID: <87a61oea66.fsf@localhost> (raw)
In-Reply-To: <167F54F2-32D1-4171-947C-B01CB19D5906@icloud.com>

Robert Nikander <robert.nikander@icloud.com> writes:

> But it doesn't seem to work like that. For example
>
>    * Testing it out
>    :LOGBOOK:
>    CLOCK: [2023-02-07 Tue 12:35]--[2023-02-07 Tue 12:45] =>  0:10
>    CLOCK: [2023-02-07 Tue 12:20]--[2023-02-07 Tue 12:30] =>  0:10
>    CLOCK: [2023-02-06 Mon 12:20]--[2023-02-06 Mon 13:20] =>  1:00
>    :END:
>
> 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.

-- 
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>


  reply	other threads:[~2023-02-08 10:42 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 [this message]
     [not found]   ` <C9F1FC5B-81DC-47B2-9359-3F191399F1B5@icloud.com>
2023-02-08 14:11     ` Robert Nikander
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=87a61oea66.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=robert.nikander@icloud.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).