emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Jeff Kowalski <jeff.kowalski@gmail.com>
Cc: emacs-orgmode@gnu.org, bhavin7392@gmail.com
Subject: Re: Bug: Duplicate logbook entry for repeated tasks [9.4.6 (9.4.6-gab9f2a @ /home/gustavo/.emacs.d/elpa/org-9.4.6/)]
Date: Sat, 26 Jun 2021 23:28:17 -0300	[thread overview]
Message-ID: <87o8bs59dq.fsf@gmail.com> (raw)
In-Reply-To: <CAG-eCj5Q++Xqzcr_XHhmovRO65j=4p7X5qtHeqA1c7QHX2SU9Q@mail.gmail.com>

Hi All,

On Sat, 26 Jun 2021 at 00:13, Jeff Kowalski <jeff.kowalski@gmail.com> 
wrote:

> While I don't have a fix for the root issue, I did have a chance to 
> create
> a lint for LOGBOOK duplicates, as you suggested.

Since Jeff put some effort, I went for some too.  :-)

I did some digging and, as far as I can tell, the commit which 
introduces the bug is "c670379ad Fix `org-agenda-todo' undo behavior 
when logging (not adding note)".

I tested the ECM initially reported, and I don't find the behavior in 
commit `b2be3dd0e', but I do find it in `59edcc27c', and what happened 
in `master' between the two is `c670379ad'.

Not a fix, but this should narrow the search down.

Best regards,
Gustavo.


  parent reply	other threads:[~2021-06-27  2:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  2:22 Bug: Duplicate logbook entry for repeated tasks [9.4.6 (9.4.6-gab9f2a @ /home/gustavo/.emacs.d/elpa/org-9.4.6/)] Jeff Kowalski
2021-06-17 13:16 ` Gustavo Barros
2021-06-26  3:13   ` Jeff Kowalski
2021-06-26 10:53     ` Gustavo Barros
2021-06-27  2:28     ` Gustavo Barros [this message]
2021-06-27  6:31       ` Bhavin Gandhi
2021-06-27 10:28         ` Gustavo Barros
2021-06-28 17:25           ` Bhavin Gandhi
  -- strict thread matches above, loose matches on Subject: below --
2021-06-14 13:39 Gustavo Barros
2021-06-14 18:01 ` Bhavin Gandhi
2021-06-14 18:41   ` Gustavo Barros

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=87o8bs59dq.fsf@gmail.com \
    --to=gusbrs.2016@gmail.com \
    --cc=bhavin7392@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jeff.kowalski@gmail.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
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).