From: Sean Whitton <spwhitton@spwhitton.name>
To: David Edmondson <dme@dme.org>, emacs-orgmode@gnu.org
Cc: notmuch@notmuchmail.org
Subject: Re: Bug: ol-notmuch.el: calls `notmuch-show' with arbitrary search query
Date: Tue, 26 Nov 2019 16:25:29 -0700 [thread overview]
Message-ID: <875zj61aqe.fsf@iris.silentflame.com> (raw)
In-Reply-To: <m2zhgi8d2x.fsf@dme.org>
Hello David,
Thank you for the investigation.
On Tue 26 Nov 2019 at 10:52PM +00, David Edmondson wrote:
> The poor behaviour is just a side effect of the way that queries are
> composed to implement the filter functionality. Does the attached patch
> help?
Unfortunately, it is still broken in my test case.
>> Further, my package 'mailscripts' tries to pass the current value of
>> `notmuch-show-thread-id' to notmuch-extract-patch(1).
>>
>> https://git.spwhitton.name/mailscripts/tree/mailscripts.el#n72
>>
>> https://manpages.debian.org/notmuch-extract-patch
>>
>> If `notmuch-show-thread-id' contains a query which returns a single
>> message, the wrong value is passed to notmuch-extract-patch(1), such
>> that it may not extract all of the patches in the thread.
>
> It's not clear to me that this is broken.
>
> notmuch-extract-patch seems to be properly extracting patches from the
> messages that match the query.
>
> If the current `notmuch-show' buffer query doesn't match the entire
> thread, why should `notmuch-extract-thread-patches' be expected to apply
> patches from the whole thread?
The purpose of `notmuch-extract-thread-patches' is to extract a whole
git-send-email(1) patch series at a time, because that is usually what
one wants to do. There are `notmuch-extract-message-patches' and
`notmuch-show-pipe-message' for single patches.
(I note that this is a mailscripts design question, not strictly
relevant to the issue of ol-notmuch.el causing the
notmuch-show-thread-id variable to be mispopulated. Thank you for your
engagement with mailscripts, regardless!)
--
Sean Whitton
next prev parent reply other threads:[~2019-11-26 23:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 21:37 Bug: ol-notmuch.el: calls `notmuch-show' with arbitrary search query Sean Whitton
2019-11-26 17:41 ` Sean Whitton
2019-11-26 19:17 ` racin
2019-11-26 21:52 ` Sean Whitton
2019-11-26 20:05 ` David Edmondson
2019-11-26 21:57 ` Sean Whitton
2019-11-26 22:52 ` David Edmondson
2019-11-26 23:25 ` Sean Whitton [this message]
2019-11-27 13:08 ` David Edmondson
2019-11-27 17:42 ` Sean Whitton
2019-11-27 20:52 ` David Edmondson
2019-11-29 20:01 ` Sean Whitton
2019-12-01 21:01 ` David Edmondson
2020-02-29 16:50 ` Sean Whitton
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=875zj61aqe.fsf@iris.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=dme@dme.org \
--cc=emacs-orgmode@gnu.org \
--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).