From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
larsi@gnus.org, 49160@debbugs.gnu.org
Subject: bug#49160: 28.0.50; [PATCH] Uninitialized inhibit_buffer_hooks
Date: Thu, 12 Jan 2023 11:25:40 -0500 [thread overview]
Message-ID: <jwvcz7jiuv5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83tu0wkxq4.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Jan 2023 09:39:47 +0200")
>> > So I'm not sure we want this. What is the real-life use case behind
>> > this request?
>>
>> The real-life use case is satisfying this bug report+patch from me,
>> fixing what seems like a simple oversight, and the ensuing peace of mind
>> that I will be grateful for, of course ;).
>
> Stefan, WDYT?
It makes the code simpler and fixes a bug, I'm all for it.
I don't think it's urgent, so it's not super important whether it goes
into `emacs-29`, OTOH.
Stefan
next prev parent reply other threads:[~2023-01-12 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 19:39 bug#49160: 28.0.50; [PATCH] Uninitialized inhibit_buffer_hooks dick
2021-06-22 11:41 ` Eli Zaretskii
2021-07-19 16:23 ` Lars Ingebrigtsen
2021-07-19 16:47 ` Eli Zaretskii
2023-01-11 20:13 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11 20:23 ` Eli Zaretskii
2023-01-11 21:16 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 7:39 ` Eli Zaretskii
2023-01-12 16:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-14 13:20 ` Eli Zaretskii
2023-01-14 14:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-17 11:08 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvcz7jiuv5.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=49160@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.