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

From: Mark Barton <mbarton98@gmail.com>
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, 8 Feb 2023 11:51:33 -0800	[thread overview]
Message-ID: <F6210EFD-975F-4445-8F33-D198F6C7B95D@gmail.com> (raw)
In-Reply-To: <830BAEAD-AA4C-4226-A93E-1329B41194D7@icloud.com>

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

next prev parent reply	other threads:[~2023-02-08 19:52 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
     [not found]   ` <C9F1FC5B-81DC-47B2-9359-3F191399F1B5@icloud.com>
2023-02-08 14:11     ` Robert Nikander
2023-02-08 19:51       ` Mark Barton [this message]
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=F6210EFD-975F-4445-8F33-D198F6C7B95D@gmail.com \
    --to=mbarton98@gmail.com \
    --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

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