discussion and development of piem
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Leo <sourcehut@relevant-information.com>, Kyle Meyer <kyle@kyleam.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH 1/1] Use notmuch-extract-patch if available
Date: Sun, 19 Dec 2021 23:45:28 -0700	[thread overview]
Message-ID: <87lf0fn59z.fsf@melete.silentflame.com> (raw)
In-Reply-To: <871r2f770q.fsf@student-228-110.eduroam.uu.se>

Hello,

On Tue 14 Dec 2021 at 12:36PM +01, Leo wrote:

> Kyle Meyer <kyle@kyleam.com> writes:
>
>> sourcehut@relevant-information.com writes:
>>> +                (if-let ((cmd (executable-find "notmuch-extract-patch"))
>>> +                         (tid
>>> +                          ;; If `notmuch-show' was called with a notmuch query rather
>>> +                          ;; than a thread ID, as `org-notmuch-follow-link' in
>>> +                          ;; org-notmuch.el does, then `notmuch-show-thread-id' might
>>> +                          ;; be an arbitrary notmuch query instead of a thread ID.  We
>>> +                          ;; need to wrap such a query in thread:{} before passing it
>>> +                          ;; to notmuch-extract-patch(1), or we might not get a whole
>>> +                          ;; thread extracted (e.g. if the query is just id:foo)
>>> +                          (if (string= (substring thread-id 0 7) "thread:")
>>> +                              thread-id
>>> +                            (concat "thread:{" thread-id "}"))))
>>
>> I believe this comment and (if ...) is coming straight from
>> mailscripts.el.  You note in the cover letter that some of this is
>> copied from mailscripts.el, but I think there should be a code comment
>> as well.
>>
>> However, I don't really understand why the condition is necessary.
>> Wouldn't always using
>>
>>   thread:{notmuch-show-get-message-id return value}
>>
>> work?
>
> I don't actually know, maybe Sean Whitton knows?

I guess if you are using the function notmuch-show-get-message-id rather
than the variable notmuch-show-thread-id, then it sounds like just
wrapping that in thread:{} would work.  But it has been some years since
I figured out that code, I'm afraid.

-- 
Sean Whitton

  reply	other threads:[~2021-12-20  6:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 20:43 [PATCH 0/1] Use notmuch-extract-patch if available sourcehut
2021-12-09 20:43 ` [PATCH 1/1] " sourcehut
2021-12-11 21:44   ` Kyle Meyer
2021-12-12  9:44     ` Leo
2021-12-12 18:45       ` Kyle Meyer
2021-12-12 19:33         ` Sean Whitton
2021-12-12 19:49           ` Kyle Meyer
2021-12-14 19:12             ` Sean Whitton
2021-12-13 11:45           ` Leo
2021-12-14 11:36     ` Leo
2021-12-20  6:45       ` Sean Whitton [this message]
2021-12-12 19:26   ` Sean Whitton
2021-12-13 11:53     ` Leo

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://git.kyleam.com/

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

  git send-email \
    --in-reply-to=87lf0fn59z.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=sourcehut@relevant-information.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.kyleam.com/piem/

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).