unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dick <dick.r.chiang@gmail.com>
Cc: 49160@debbugs.gnu.org
Subject: bug#49160: 28.0.50; [PATCH] Uninitialized inhibit_buffer_hooks
Date: Tue, 22 Jun 2021 14:41:17 +0300	[thread overview]
Message-ID: <83fsxaunxe.fsf@gnu.org> (raw)
In-Reply-To: <874kdratxt.fsf@dick> (message from dick on Mon, 21 Jun 2021 15:39:26 -0400)

> From: dick <dick.r.chiang@gmail.com>
> Date: Mon, 21 Jun 2021 15:39:26 -0400
> 
> It's random whether buffers created outside `get-buffer-create`, i.e.,
> indirect buffers, call kill-buffer hooks.

Please in the future try to be more explicit in describing the
problem.  "It is random" isn't explicit enough.

More to the point: since this attribute of a buffer cannot be changed
once the buffer is created, I think it might be okay to copy from the
base buffer, but we should also allow the caller to control that by
introducing an optional argument similar to that of get-buffer-create.
And if we do that, we could also consider making the default value be
nil, not necessarily a copy of that of the base buffer.

Thanks.





  reply	other threads:[~2021-06-22 11:41 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 [this message]
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
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

  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=83fsxaunxe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=49160@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.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.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).