From: Daniel Clemente <n142857@gmail.com>
To: Org-mode Org-Mode <emacs-orgmode@gnu.org>
Subject: [BUG] Shift-up/down move the cursor to end of timestamp
Date: Fri, 2 Dec 2022 05:17:27 +0000 [thread overview]
Message-ID: <CAJKAhPDVs5GRKR-cmyeNd5cQFHyKpw_=JptBzi1f0FYNTqqjzA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Hi.
Using a file with just one header:
* something
:CLOCK:
CLOCK: [2022-12-01 Thu 17:15]--[2022-12-01 Thu 17:30] => 0:15
:END:
If I put the cursor on the end timestamp (on the 3 of 17:30) and press
shift+up or shift-down, the timestamp is correctly adjusted by 5 minutes,
but the cursor jumps some characters to the right and stays at the right of
]
It should stay on the same character (the 3), so that I can keep adjusting
the minutes with shift-up/down
Tested on: GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit,
cairo version 1.16.0, Xaw scroll bars) of 2022-11-18
No other settings needed in your .emacs
I bisected the tree until I found in which commit this started. Copying
from git bisect:
5bc6741a5abd42e8305bb0fcfe78801813309640 is the first bad commit
commit 5bc6741a5abd42e8305bb0fcfe78801813309640
Author: Ihor Radchenko <yantar92@posteo.net>
Date: Tue Nov 1 15:52:25 2022 +0800
org-clock-update-time-maybe: Update the containing timestamps as well
* lisp/org-clock.el (org-clock-update-time-maybe): Update the
containing timestamps inside the clock, not only the clock sum.
Reported-by: Bruce E. Robertson <brucer42@gmail.com>
Link: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53393
lisp/org-clock.el | 35 ++++++++++++++++++++++++-----------
1 file changed, 24 insertions(+), 11 deletions(-)
[-- Attachment #2: Type: text/html, Size: 1853 bytes --]
next reply other threads:[~2022-12-02 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 5:17 Daniel Clemente [this message]
2022-12-03 3:08 ` [BUG] Shift-up/down move the cursor to end of timestamp Christopher M. Miles
2022-12-07 10:52 ` Ihor Radchenko
2022-12-07 10:53 ` Ihor Radchenko
2022-12-07 19:34 ` Daniel Clemente
2023-01-12 9:23 ` Johannes Dahl
2023-01-13 9:11 ` 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='CAJKAhPDVs5GRKR-cmyeNd5cQFHyKpw_=JptBzi1f0FYNTqqjzA@mail.gmail.com' \
--to=n142857@gmail.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).