unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Brian May <brian@linuxpenguins.xyz>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	notmuch@notmuchmail.org
Subject: Re: Weird tagging issue
Date: Sun, 22 Mar 2020 22:12:14 -0300	[thread overview]
Message-ID: <87imivlvrl.fsf@tethera.net> (raw)
In-Reply-To: <87r1xkt784.fsf@silverfish.pri>

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

Brian May <brian@linuxpenguins.xyz> writes:

> Hmmmm. Maybe the References header is bad. I see a number of emails in
> this thread referencing "pr-wspdigital/bupaoshc/88@bitbucket.org", e.g.:
>
> === cut ===
> References: <pr-wspdigital/bupaoshc/88@bitbucket.org>
>  <prcomment-140582662@bitbucket.org>
>
> References: <pr-wspdigital/bupaoshc/88@bitbucket.org>
>
> References: <pr-wspdigital/bupaoshc/88@bitbucket.org>
>  <pr-wspdigital/bupaoshc/88@bitbucket.org>
> === cut ===
>
> But "pr-wspdigital/bupaoshc/88@bitbucket.org" doesn't have any
> information uniquely identifying a particular message for PR #88, and
> furthermore I don't see any message ids that look like this in this
> thread.
>
> I could imagine bad references might be confusing notmuch?


If you still have the messages, maybe you could try the attached script
to visualize the reference structure.

I think dkg and I agreed a few years ago we should ship is as one of our
devel tools, but then I didn't follow through. So I'd be interested in
knowing if it works for you.


[-- Attachment #2: draw-thread --]
[-- Type: application/octet-stream, Size: 912 bytes --]

#!/bin/bash

# This script can be used like
# NOTMUCH_CONFIG=test/tmp.T580-thread-search/notmuch-config \
#    devel/draw-thread thread:0000000000000002 | dot -Tpdf > thread2.pdf

# In addition to notmuch, you will need the following tools installed
# - graphviz
# - formail (part of procmail)

threadid=$1

declare -a edges

declare -a dest
echo "digraph \"$threadid\" {"
for messageid in $(notmuch search --output=messages $threadid); do
    echo "subgraph \"cluster_$messageid\" {"
    printf "\"%s\" [shape=folder];\n" ${messageid#id:}
    for file in $(notmuch search --output=files $messageid); do
        node=$(basename $file)
        printf "\"%s\" [shape=note];\n" $node

        mapfile -t dest < <(formail -x references < $file | tr '<>,' '"" ')
        edge="\"$node\" -> { ${dest[*]} }"
        edges+=($edge)
    done
    echo "}"
done

for edge in "${edges[*]}"; do
    echo $edge
done

echo "}"

  reply	other threads:[~2020-03-23  1:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  4:27 Weird tagging issue Brian May
2020-03-20  0:06 ` Brian May
2020-03-21  1:03   ` Daniel Kahn Gillmor
2020-03-22 21:22     ` Brian May
2020-03-23  1:12       ` David Bremner [this message]
2020-03-23  2:58         ` Daniel Kahn Gillmor
2020-03-29 21:03         ` Brian May
2020-03-29 23:19           ` Daniel Kahn Gillmor
2020-03-29 23:55             ` Brian May
2020-03-30  0:53               ` Carl Worth
2020-03-30  5:22                 ` Daniel Kahn Gillmor
2020-03-30 21:16                   ` Brian May

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=87imivlvrl.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=brian@linuxpenguins.xyz \
    --cc=dkg@fifthhorseman.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).