From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id mNNID47942NMuAAAbAwnHQ (envelope-from ) for ; Wed, 08 Feb 2023 20:52:46 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id 2Ig2Do7942NBzAAAG6o9tA (envelope-from ) for ; Wed, 08 Feb 2023 20:52:46 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C86457F99 for ; Wed, 8 Feb 2023 20:52:45 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pPqTz-0008WV-3c; Wed, 08 Feb 2023 14:51:55 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pPqTv-0008Vi-49 for emacs-orgmode@gnu.org; Wed, 08 Feb 2023 14:51:52 -0500 Received: from mail-pl1-x62d.google.com ([2607:f8b0:4864:20::62d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pPqTr-0002yy-9a for emacs-orgmode@gnu.org; Wed, 08 Feb 2023 14:51:50 -0500 Received: by mail-pl1-x62d.google.com with SMTP id be8so36272plb.7 for ; Wed, 08 Feb 2023 11:51:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=sapTpQx8vvpjoogc2gFejpGxhh9chtDJdZfl4zonI+o=; b=OHGbmzAzXklXLqFUsWgzgWLlx3JJrIvc/pzBOW2e2vhDSU1TjkFpArDVuG7iB/e0ab /swHEsxEV1E5KhE5sJW4TntOJGwYnzhNHfC4ONuGdml9Q1r+wdmUsaYiUgJD7BVGeQkm qcDqoRIuxcQYPoCeti8pnQTGqfSfPUyodVBQsKEDXkl5JI2b1nlT51jSbxu0aXKN6jx4 lA8s15PfoTw3Odok2IIbfobQds78GzOL1LO1lloUXyjaqChtUii0VrpZEUCYyOsJ5ScT sNsAZpqfM8c9DY+hW0rybSHEgqyog+9AGPt/XDAyH980KrDJoVbNDwyNJY/TRm//kxz+ 3QLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=sapTpQx8vvpjoogc2gFejpGxhh9chtDJdZfl4zonI+o=; b=ggFO8BVhsR6cJE6V9QziYmQa1X1fHVchIFpG2NGqoC4zgk43Ida7NseWRJ4tRW3Bav h+MUlOrajqH+O6Zcu0iWEcGpZtx00KTi3FH9EiJUdvaYAYRRYL2+vqtS9+gJNLKeE8ar i2x6dPtnnXxvaahtcHdN/Lp0ZaNSKnw4Y0tBj/z1xxr1792FNpOwCODBum3KPrg02JX0 QSZXF6JDRLzDUL2ii6FhUWmxbpynIW5NvMbGythjsaydMpw8J/zfP7oQqx70hk/0/3Ku WhnEoGzw0N6vKsr/Mm6xDKiwVmTIhqKvnGjm2SEkpzcNXlf8cFVgIYiQlx6imZ0WPB9l u1zg== X-Gm-Message-State: AO0yUKXrjdccZONtUxarx4MUP1dc0oaPKVrCjOsuT9gNzURLDE8j5yhL bFnnGpxq5hXjFyhbF76SrMs= X-Google-Smtp-Source: AK7set++NmaVtJTr5M5X2eybJNqLzhNWnS8W3FDq6244rdvmJlU0fNvqcGCZB2wbOvFDFM6Hx2BThg== X-Received: by 2002:a17:902:e38a:b0:198:e3ee:2c95 with SMTP id g10-20020a170902e38a00b00198e3ee2c95mr6557699ple.7.1675885905307; Wed, 08 Feb 2023 11:51:45 -0800 (PST) Received: from smtpclient.apple (2603-8001-7a00-01a0-2405-b8cc-c651-cf79.res6.spectrum.com. [2603:8001:7a00:1a0:2405:b8cc:c651:cf79]) by smtp.gmail.com with ESMTPSA id q3-20020a170902b10300b00198ac2769b6sm7670516plr.83.2023.02.08.11.51.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2023 11:51:44 -0800 (PST) From: Mark Barton Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_810C9583-AEEE-4F1D-871B-DFFC2FF21FC8" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\)) Subject: Re: [BUG] M-S- does not adjust clock timestamps as described in docs [9.5.5] Date: Wed, 8 Feb 2023 11:51:33 -0800 In-Reply-To: <830BAEAD-AA4C-4226-A93E-1329B41194D7@icloud.com> Cc: emacs-orgmode@gnu.org To: Robert Nikander References: <167F54F2-32D1-4171-947C-B01CB19D5906@icloud.com> <87a61oea66.fsf@localhost> <830BAEAD-AA4C-4226-A93E-1329B41194D7@icloud.com> X-Mailer: Apple Mail (2.3731.300.101.1.3) Received-SPF: pass client-ip=2607:f8b0:4864:20::62d; envelope-from=mbarton98@gmail.com; helo=mail-pl1-x62d.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1675885965; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=sapTpQx8vvpjoogc2gFejpGxhh9chtDJdZfl4zonI+o=; b=kAaVyTDgl1YzXhwZ8APSc5FF//Sk42sZB2X17BXtmso+jOH+VdP5SrFJ71pJ+tPQi1ZZyk GTb2cIihR+1HkODfr++EB0w1zZrvP2dbtJWEU7sjKq9dfY2nLLIg84Ewkgw0FVEJZvWNEu IgpH/T9EApsMea6g7sDE1ltvBGnQfpF5eN4h3FtF5sNIKpu+fhEFxwS++AgNTkwQ7tn2Wh gK2lD7zwAWSXv1AnrwAOFNgRnlYYM7q34AOfLbDiuNmV+NDzA4+KM30Amngbf1ponHQX5Y XXU/PvJWiP5WO2LsVR/WoRSCGVHvN0IgAXy4jgCpNBvKaacSE4p6OgbIYnexJQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=OHGbmzAz; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1675885965; a=rsa-sha256; cv=none; b=Ki0Lx5yXAHA0JpnEhC8ycEsnTroQOv8/3cD6n5BwuB5BwthKvw16vGuwqGHs6vWma/OwHy fetxBIZXA97F2MJiJNuvx1iXZHi3vng/AH4h4+U66qgk90yOT8Ut6kcwNjghJYT6CupC/e 8KRklVEYqhlTCtoqSbGG9urL+W9HT8MNChfFeuFTksoRoeRwt+eH2lrnNRCuXG6Ap2Qb4Z XgEbVRMQBBM8Xz0arC7yi2U4+fW5kK+7+bck0eiaQeoSLeY6VSqSMYsArvd2d+xoDG8ZGk GKwCAcxum3iYARYljJSZsNFfALZNwnfQlpcMKGeuO+Y1aZqfs0i9PxCW3z6TQA== X-Spam-Score: -11.85 X-Migadu-Queue-Id: C86457F99 X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=OHGbmzAz; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com X-Migadu-Spam-Score: -11.85 X-TUID: ll9LM34WGX96 --Apple-Mail=_810C9583-AEEE-4F1D-871B-DFFC2FF21FC8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Feb 8, 2023, at 6:11 AM, Robert Nikander = wrote: >=20 > I=E2=80=99m pretty much a beginner with the clock features, so I = don=E2=80=99t have an opinion yet on how it should work. But yes, it = seems like clarifying the manual there would be an improvement.=20 >=20 > I don=E2=80=99t know what agenda clock check is. Is that a certain = function, or agenda view? Searching the manual and functions for that = term didn=E2=80=99t 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.=20 Mark= --Apple-Mail=_810C9583-AEEE-4F1D-871B-DFFC2FF21FC8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Feb = 8, 2023, at 6:11 AM, Robert Nikander <robert.nikander@icloud.com> = wrote:

I=E2=80=99m pretty much = a beginner with the clock features, so I don=E2=80=99t have an opinion = yet on how it should work. But yes, it seems like clarifying the manual = there would be an improvement. 

I don=E2=80=99t know what agenda clock = check is. Is that a certain function, or agenda view? Searching the = manual and functions for that term didn=E2=80=99t 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.

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
= --Apple-Mail=_810C9583-AEEE-4F1D-871B-DFFC2FF21FC8--