unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Al Haji-Ali <abdo.haji.ali@gmail.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Correcting message references
Date: Tue, 25 Apr 2023 22:20:49 +0100	[thread overview]
Message-ID: <m2ildj8xqm.fsf@gmail.com> (raw)
In-Reply-To: <87ildjn41q.fsf@tethera.net>


On 25/04/2023, David Bremner wrote:
> I would be interested if it finds your problematic ghost message (and
> how long it takes).

Thanks! This is much quicker than a script that I wrote using quest and xapian-delve (which took
minutes!)

Your code took 0.03 seconds to find 74 unreferenced ghost messages out of 9335 ghost messages,
I can't imagine why so many un-referenced ghost messages were
created. 47 of the 74 messages have "draft" in the ID (seemingly created by notmuch).

At first your code didn't find my problematic message (which caused a draft with the ID <jwvczk7opm8.fsf-monnier+emacs@gnu.org> in `In-Reply-To` to be grouped with unrelated messages from a completely separate thread).
But then I deleted the draft (including the file), ran `notmuch new` and re-ran the script and the problematic ghost message was correctly reported.

So this approach would work to find un-referenced messages, but not messages which are being erroneously grouped (without first deleting the offending message), correct?

-- Al

      reply	other threads:[~2023-04-25 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 15:11 Correcting message references Al Haji-Ali
2023-04-22 11:09 ` David Bremner
2023-04-22 12:20   ` Al Haji-Ali
2023-04-22 16:37     ` David Bremner
2023-04-22 16:44       ` David Bremner
2023-04-23  8:19       ` Al Haji-Ali
     [not found]         ` <87r0s8141e.fsf@tethera.net>
2023-04-25 19:40           ` David Bremner
2023-04-25 21:20             ` Al Haji-Ali [this message]

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2ildj8xqm.fsf@gmail.com \
    --to=abdo.haji.ali@gmail.com \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).