From: Jai Flack <jflack@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54662@debbugs.gnu.org
Subject: bug#54662: 29.0.50; [PATCH] An mu backend for gnus-search
Date: Mon, 04 Apr 2022 12:29:13 +0000 [thread overview]
Message-ID: <87ee2dav6u.fsf@posteo.net> (raw)
In-Reply-To: <87lewlgmyk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 04 Apr 2022 12:30:27 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Jai Flack <jflack@posteo.net> writes:
>
>> I'm not sure if you read the discussion on emacs-devel but the issue of
>> having a duplicate feature in-tree and as a package for Emacs 28 was
>> briefly discussed without solution.
>
> No, didn't read that. Does that mean that the ELPA package doesn't work
> in Emacs 29?
The package works fine, it just redefines some symbols (to an identical
definition); I would just prefer to avoid duplicated code if possible.
I'm not sure how many users there would be of this as an ELPA package
for one Emacs version so it's very possible it's not worth the effort.
--
Thanks,
Jai
(Can never seem to get signed emails from Gnus that also look right in
plaintext)
next prev parent reply other threads:[~2022-04-04 12:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 1:39 bug#54662: 29.0.50; [PATCH] An mu backend for gnus-search Jai Flack via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 14:58 ` Lars Ingebrigtsen
2022-04-02 15:13 ` Corwin Brust
2022-04-02 15:25 ` Eric Abrahamsen
2022-04-02 15:28 ` Corwin Brust
2022-04-02 16:12 ` Eric Abrahamsen
2022-04-02 16:14 ` Corwin Brust
2022-04-03 2:28 ` Jai Flack
2022-04-02 15:21 ` Eric Abrahamsen
2022-04-02 15:26 ` Lars Ingebrigtsen
2022-04-03 2:26 ` Jai Flack
2022-04-03 12:00 ` Lars Ingebrigtsen
2022-04-03 14:53 ` Jai Flack
2022-04-04 10:30 ` Lars Ingebrigtsen
2022-04-04 12:29 ` Jai Flack [this message]
2022-04-06 9:15 ` Lars Ingebrigtsen
2022-04-06 23:31 ` Jai Flack
2022-04-07 11:14 ` Lars Ingebrigtsen
2022-04-07 11:26 ` Jai Flack
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee2dav6u.fsf@posteo.net \
--to=jflack@posteo.net \
--cc=54662@debbugs.gnu.org \
--cc=larsi@gnus.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://git.savannah.gnu.org/cgit/emacs.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).