From: "Jorge P. de Morais Neto" <jorge+list@disroot.org>
To: emacs-orgmode@gnu.org
Subject: S-M-{<UP>,<DOWN>} on CLOCK timestamp
Date: Sat, 21 Aug 2021 19:16:19 -0300 [thread overview]
Message-ID: <87sfz2zbnw.fsf@disroot.org> (raw)
Keywords: org-timestamp-down org-timestamp-up
Hi. Suppose the buffer has the following text:
* Task A
:LOGBOOK:
CLOCK: [2021-08-21 sáb 18:00]--[2021-08-21 sáb 18:10] => 0:10
:END:
* Task B
:LOGBOOK:
CLOCK: [2021-08-21 sáb 18:18]
:END:
If I invoke M-S-<down> on Task B's clock-in timestamp, with point right
after the colon that separates HH from MM, then it correctly changes to
18:15 (decreases by three minutes), but Task A's clock-out timestamp
changes to 18:05---decreases by *five* minutes.
In my opinion, in this case the previous clock-out timestamp should not
change at all, because it was already less than 18:15. But even if you
do think it should change, then surely you at least agree that it should
change by *three* minutes, just like Task A's clock-in timestamp.
This occurs on GNU Emacs 28.0.50 installed with
~guix package --with-branch=emacs-next=master -i emacs-next~
(upgraded last Thursday morning), invoked as ~emacs -Q~. Note that on
my Guix-installed Emacs, an ~emacs -Q~ does load the emacs-org Guix
package (version 9.4.6). Note also that my Org Mode has been patched
with Ihor Radchenko's patch to org-clock.el (attached to my previous
message), but it clearly can't influence this problem.
Regards
Emacs : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
Package: Org mode version 9.4.6 (9.4.6-gab9f2a @ /gnu/store/yg6kjzigqyfzbkzj99xmwmv3nssvhvnq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)
--
- Disinformation flourishes because many people care about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
- I am Brazilian. I hope my English is correct and I welcome feedback.
- Free Software Supporter: https://www.fsf.org/free-software-supporter
- If an email of mine arrives at your spam box, please notify me.
next reply other threads:[~2021-08-21 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 22:16 Jorge P. de Morais Neto [this message]
2021-08-22 1:21 ` S-M-{<UP>,<DOWN>} on CLOCK timestamp Tim Cross
2021-08-22 13:55 ` Jorge P. de Morais Neto
2021-09-10 6:21 ` Timothy
2021-09-13 8:06 ` Tim Cross
2021-09-24 22:22 ` Tim Cross
2021-11-02 14:30 ` Jorge P. de Morais Neto
2024-01-18 15:38 ` 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=87sfz2zbnw.fsf@disroot.org \
--to=jorge+list@disroot.org \
--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).