discussion and development of piem
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH v2 3/5] piem: Add piem-inbox-by-gnu-package-match.
Date: Sat, 10 Jun 2023 12:08:25 +0200	[thread overview]
Message-ID: <87h6rfmxye.fsf@fsfe.org> (raw)
In-Reply-To: <87sfazncc8.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> writes:

> jlicht@fsfe.org writes:
>
>> diff --git a/piem.el b/piem.el
>> index 914dd23..3fffb0e 100644
>> --- a/piem.el
>> +++ b/piem.el
>> @@ -490,6 +490,21 @@ non-nil, make the match specific for that message."
>>                    (mail-decode-encoded-word-string val)))
>>                headers))))
>>  
>> +(defun piem-inbox-by-gnu-package-match (gnu-package)
>> +  "Return inbox based on matching :gnu-package properties.
>> +GNU-PACKAGE should be a string. This function is intended to be
>
> Convention: two spaces after period

Done in V3. Any setting or .dir-locals I can use to not consistently
keep forgetting to do this?

>> +used by libraries implementing a function for
>> +`piem-get-inbox-function'."
>> +  (when gnu-package
>> +    (catch 'hit
>> +      (dolist (inbox (piem-merged-inboxes))
>> +        (let* ((info (cdr inbox))
>> +               (p-package (plist-get info :gnu-package)))
>> +          (when (and gnu-package
>> +                     p-package
>> +                     (string-match-p p-package gnu-package))
>> +            (throw 'hit (car inbox))))))))
>> +
>
> I think it's nice to have this as a separate function, and I'm guessing
> its use in the upcoming piem-debbugs.el is one of the reasons you
> decided to do that.
>
> But perhaps piem-inbox-by-gnu-package-match should still be called in
> piem-inbox-by-header-match, following the dolist there.  The main
> advantage of that is that debbugs.el also has Rmail support, so it'd let
> piem-rmail-get-inbox take advantage of this header too.  Plus, if
> piem-notmuch users want to match against X-GNU-PR-PACKAGE for whatever
> reason, even though they should have a List-ID too, it seems like we
> might as well consistently support it.

Done in V3.

  reply	other threads:[~2023-06-10 10:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 16:59 [PATCH 1/2] piem: Add :gnu-package keyword to piem-inboxes jlicht
2023-06-08 16:59 ` [PATCH 2/2] gnus: Skip adding mboxrd from-line when not needed jlicht
2023-06-09 12:48 ` [PATCH v2 0/5] New piem-debbugs integration jlicht
2023-06-09 12:48   ` [PATCH v2 1/5] piem: Add :gnu-package keyword to piem-inboxes jlicht
2023-06-10  4:52     ` Kyle Meyer
2023-06-10 10:02       ` Jelle Licht
2023-06-09 12:48   ` [PATCH v2 2/5] gnus: Skip adding mboxrd from-line when not needed jlicht
2023-06-10  4:55     ` Kyle Meyer
2023-06-10 10:07       ` Jelle Licht
2023-06-09 12:48   ` [PATCH v2 3/5] piem: Add piem-inbox-by-gnu-package-match jlicht
2023-06-10  4:57     ` Kyle Meyer
2023-06-10 10:08       ` Jelle Licht [this message]
2023-06-09 12:48   ` [PATCH v2 4/5] gnus: Add support for matching inbox by X-GNU-PR-PACKAGE header jlicht
2023-06-10  4:58     ` Kyle Meyer
2023-06-10 10:08       ` Jelle Licht
2023-06-09 12:48   ` [PATCH v2 5/5] Add basic integration for debbugs jlicht
2023-06-10  4:59     ` Kyle Meyer
2023-06-10 10:11       ` Jelle Licht
2023-06-10  5:00   ` [PATCH v2 0/5] New piem-debbugs integration Kyle Meyer
2023-06-10  9:58 ` [PATCH v3 " jlicht
2023-06-10  9:58   ` [PATCH v3 1/5] piem: Add :gnu-package keyword to piem-inboxes jlicht
2023-06-10  9:58   ` [PATCH v3 2/5] gnus: Skip adding mboxrd from-line when not needed jlicht
2023-06-10  9:58   ` [PATCH v3 3/5] piem: Add piem-inbox-by-gnu-package-match jlicht
2023-06-10 23:17     ` Kyle Meyer
2023-06-10  9:58   ` [PATCH v3 4/5] piem-inbox-by-header-match: Fallback to matching via :gnu-package jlicht
2023-06-10  9:58   ` [PATCH v3 5/5] Add basic integration for debbugs jlicht
2023-06-10 23:16   ` [PATCH v3 0/5] New piem-debbugs integration Kyle Meyer
2023-06-10 23:46     ` Jelle Licht
2023-06-11  0:55       ` Kyle Meyer

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=87h6rfmxye.fsf@fsfe.org \
    --to=jlicht@fsfe.org \
    --cc=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.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).