* [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
@ 2023-02-07 21:46 Robert Nikander
2023-02-08 10:14 ` Ihor Radchenko
0 siblings, 1 reply; 5+ messages in thread
From: Robert Nikander @ 2023-02-07 21:46 UTC (permalink / raw)
To: emacs-orgmode
Hi,
The docs say this about S-M + arrow keys on clock log lines. (In section: 8.4.1 - Dates and Times > Clocking Work Time > Clocking Commands)
‘S-M-<UP>’ (‘org-timestamp-up’)
‘S-M-<DOWN>’ (‘org-timestamp-down’)
On ‘CLOCK’ log lines, increase/decrease the timestamp at point and
the one of the previous, or the next, clock timestamp by the same
duration. For example, if you hit ‘S-M-<UP>’ to increase a
clocked-out timestamp by five minutes, then the clocked-in
timestamp of the next clock is increased by five minutes.
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.
Rob
Emacs : GNU Emacs 28.2 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60 Version 10.14.6 (Build 18G95))
of 2022-09-12
Package: Org mode version 9.5.5 (release_9.5.5 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
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>
0 siblings, 1 reply; 5+ messages in thread
From: Ihor Radchenko @ 2023-02-08 10:14 UTC (permalink / raw)
To: Robert Nikander; +Cc: emacs-orgmode
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>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
[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
0 siblings, 2 replies; 5+ messages in thread
From: Robert Nikander @ 2023-02-08 14:11 UTC (permalink / raw)
To: emacs-orgmode
> 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
2023-02-08 14:11 ` Robert Nikander
@ 2023-02-08 19:51 ` Mark Barton
2023-02-09 9:58 ` Ihor Radchenko
1 sibling, 0 replies; 5+ messages in thread
From: Mark Barton @ 2023-02-08 19:51 UTC (permalink / raw)
To: Robert Nikander; +Cc: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
> On Feb 8, 2023, at 6:11 AM, Robert Nikander <robert.nikander@icloud.com> wrote:
>
> 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.
Here is an option that I have been using for a few years now, in case it helps you find your solution.
I use org agenda view with log mode on to show clocked entries. The "v c" keys bring up the view of clock check
C-c a a l v c
Now to adjust the gaps or overlaps in clocking, I found this package helpful versus doing it manually for the entries.
https://github.com/dfeich/org-clock-convenience
I can go to a clock entry that needs adjustment and run the org-clock-convenience-fill-gap command and it will adjust the time to be contiguous.
Mark
[-- Attachment #2: Type: text/html, Size: 2963 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
2023-02-08 14:11 ` Robert Nikander
2023-02-08 19:51 ` Mark Barton
@ 2023-02-09 9:58 ` Ihor Radchenko
1 sibling, 0 replies; 5+ messages in thread
From: Ihor Radchenko @ 2023-02-09 9:58 UTC (permalink / raw)
To: Robert Nikander; +Cc: emacs-orgmode
Robert Nikander <robert.nikander@icloud.com> writes:
> 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.
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5d548c34f
--
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>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-02-09 9:59 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2023-02-08 19:51 ` Mark Barton
2023-02-09 9:58 ` Ihor Radchenko
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).