emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Robert Nikander <robert.nikander@icloud.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5]
Date: Tue, 7 Feb 2023 16:46:32 -0500	[thread overview]
Message-ID: <167F54F2-32D1-4171-947C-B01CB19D5906@icloud.com> (raw)

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

next             reply	other threads:[~2023-02-07 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 21:46 Robert Nikander [this message]
2023-02-08 10:14 ` [BUG] M-S-<UP> does not adjust clock timestamps as described in docs [9.5.5] 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

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=167F54F2-32D1-4171-947C-B01CB19D5906@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

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