Re: Recommended method to pair Notmuch with Neovim?

2023-04-23 Thread Ralph Seichter
Side note for the morbidly curious: Getting notmuch-vim operational on
my production servers took some work. Gentoo Linux's net-mail/notmuch
ebuild does not currently create Ruby bindings (only Python).

Given that Gentoo supports packages having multiple versions installed
simultaneously, Ruby for instance, extending the ebuild is not trivial.
I got it working specifically for my own machines, but my ebuild variant
would not yet pass Gentoo's QA checks.

-Ralph
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org


Re: Correcting message references

2023-04-23 Thread Al Haji-Ali


On 22/04/2023, David Bremner wrote:
> You need to give the appropriate term prefix. Q for message id,
> or XREPLYTO or XREFERENCE as in my last message.
My apologies. I misunderstood the syntax.

>> The first one is the draft. The second hit is the reason I thought the
>> only place left for notmuch to associate these messages is in the
>> xapian database. Note that if I delete the draft and reindex, only the
>> postlist.glass hit stubbornly remains and there seems to be no way to
>> make notmuch forget about this ID.
>
> As long as some message refers to that ID, notmuch will create a "ghost
> message", used for threading.
I've deleted all messages/draft referring to this message ID, then got these 
results:


$ export MSG_ID=jwvczk7opm8.fsf-monnier+em...@gnu.org
$ export NM_DB=~/.mail/.notmuch/xapian

$ xapian-delve -d $NM_DB -t "XREPLYTO${MSG_ID}"
term 'xreplytojwvczk7opm8.fsf-monnier+em...@gnu.org' not in database

$ xapian-delve -d $NM_DB -t "XREFERENCE${MSG_ID}"
term 'xreferencejwvczk7opm8.fsf-monnier+em...@gnu.org' not in database

$ quest -btype:T -b id:Q -d ~/.mail/.notmuch/xapian "id:${MSG_ID}"
Parsed Query: Query(0 * (qjwvczk7opm8.fsf-monnier+em...@gnu.org AND Tghost))
Exactly 1 matches
MSet:
75982: [0]

$ xapian-delve -d $NM_DB -r 75982 -1
Data for record #75982:

Term List for record #75982:
Gcc96
qjwvczk7opm8.fsf-monnier+em...@gnu.org
Tghost


So it does seem to be a lingering ghost message, but I am sure that there are 
no messages in the database referring to this ID (except messages in this 
current thread which have the ID in the message body).
I don't know why this particular ID is associated to messages in another 
seemingly unrelated thread as you in the pdf.

Is there a way to remove this ghost message record somehow to test it? Or is 
there a better way of figuring this out.

Best regards,
-- Al
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org