From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Gilles <gilles.usenet@gmail.com>,
"54161@debbugs.gnu.org" <54161@debbugs.gnu.org>
Subject: bug#54161: [External] : bug#54161: 27.2; `define-minor-mode' with alist of key bindings
Date: Tue, 01 Mar 2022 23:52:07 +0100 [thread overview]
Message-ID: <8735k1l208.fsf@gnus.org> (raw)
In-Reply-To: <875yoxmi48.fsf@web.de> (Michael Heerdegen's message of "Tue, 01 Mar 2022 23:18:47 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> You said there was no bug - nothing to fix. Guess it depends on who
>> reports there's a problem to fix.
The text was fine before, and it's fine after the change, too.
> But yes Lars, would be good if people who normally read emacs-bug daily
> have a chance to look at new reports before they are already closed.
I close bugs that I don't think needs further work. If you disagree
with that, you can still work on the bugs, of course -- whether the bug
is "closed" or not doesn't make a difference.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-01 22:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 17:48 bug#54161: 27.2; `define-minor-mode' with alist of key bindings Drew Adams
2022-02-25 21:41 ` Gilles
2022-02-26 3:20 ` bug#54161: [External] : " Drew Adams
2022-02-28 9:46 ` Lars Ingebrigtsen
2022-03-01 1:21 ` Michael Heerdegen
2022-03-01 15:41 ` Lars Ingebrigtsen
2022-03-01 18:16 ` bug#54161: [External] : " Drew Adams
2022-03-01 22:18 ` Michael Heerdegen
2022-03-01 22:52 ` Lars Ingebrigtsen [this message]
2022-03-01 23:56 ` Michael Heerdegen
2022-03-02 0:04 ` Michael Heerdegen
2022-03-01 18:11 ` Drew Adams
2022-02-25 22:33 ` Drew Adams
2022-02-25 22:43 ` Drew Adams
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=8735k1l208.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54161@debbugs.gnu.org \
--cc=gilles.usenet@gmail.com \
--cc=michael_heerdegen@web.de \
/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).