From: Jelle Licht <jlicht@fsfe.org>
To: piem@inbox.kyleam.com
Subject: On the road to (GNU) debbugs support, some blockers
Date: Sat, 27 May 2023 16:12:43 +0200 [thread overview]
Message-ID: <87y1l9ualg.fsf@fsfe.org> (raw)
Thanks for working on piem, and sharing it under a free license!
In getting some local hacks set up, I ran into some inconsistencies and
issues, which may very well be misunderstandings on my part.
The first one:
the public-inbox-config man page (`man 5 public-inbox-config') demonstrates a
url without trailing '/'. Piem's documentation uses an url with trailing '/'.
It seems `piem-b4--get-am-files' assumes this url always has a trailing
'/', which makes it not work for the examples used in the
public-inbox-config manpage (and in particular, my pre-existing
configuration). I'm not unsure if public inbox supports the trailing
'/', but I see no reason to assume it would not.
The second issue; in order to map (GNU) debbugs data to inbox
configurations, the current best way I've worked out is to use the
X-GNU-PR-Package header.
Concretely, I've had to adjust `piem-gnus-get-inbox' to also take this
particular mail header into account when trying to find matching
configured inboxes. I am not aware of a way for debbugs users to be able
to use this, without messing with non-debbugs users of gnus. Advice
appreciated.
NB, I also added the `:gnu-pr-package' to my configured piem inboxes so
the matching could take place in the first place, of course, but this is
already possible with via {setq,Customize system,$HOME.public-inbox/config}.
Third issue:
The `piem-gnus-mid-to-thread' seems to prepend a line like: "From
mboxrd@z Thu Jan 1 00:00:00 1970" to entries. The issue comes up when we
already have a line that starts with "From " at the top, which after
running the `replace-regexp-in-string' boils down to something like in
my generated m-piem file:
--8<---------------cut here---------------start------------->8---
From mboxrd@z Thu Jan 1 00:00:00 1970
>From unknown Sat May 27 07:31:53 2023
[rest of file]
--8<---------------cut here---------------end--------------->8---
AFAIK, b4 am can't deal with this, as the "From " line needs to be the
first line, and any later lines need to be parsed as email header (which
">From ..." is not). Any solutions appreciated, that (again) don't
impact non-debbugs users of gnus. My local current hack changed the
format string "From mboxrd@z Thu Jan 1 00:00:00 1970\n%s\n" by "%s\n",
and the regex from "^>*From " into "^>+From", but this will of course
break if any of the mails I'm working with contains a line starting with
"From ".
Thanks for any help, and please let me know if you'd be interested
patches for a (clean) integration with (GNU) debbugs.
Kind regards,
Jelle Licht
next reply other threads:[~2023-05-27 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 14:12 Jelle Licht [this message]
2023-05-31 4:05 ` On the road to (GNU) debbugs support, some blockers Kyle Meyer
2023-06-02 10:49 ` Jelle Licht
2023-06-03 2:34 ` Kyle Meyer
2023-06-03 5:34 ` Kyle Meyer
2023-06-03 4:49 ` 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=87y1l9ualg.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--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).