all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Constantin Kulikov <zxnotdead@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: kill-buffer calls frame's buffer-predicate for all buffers even if the killed buffer was not shown in any window.
Date: Wed, 18 Jan 2017 17:43:01 +0200	[thread overview]
Message-ID: <83fukg8jcq.fsf@gnu.org> (raw)
In-Reply-To: <CAFkz2ypw-ynu8+GyMa=j-OzWXED8LZ=96AXp+GSOGaXDTT0sOA@mail.gmail.com> (message from Constantin Kulikov on Wed, 18 Jan 2017 13:03:08 +0300)

> From: Constantin Kulikov <zxnotdead@gmail.com>
> Date: Wed, 18 Jan 2017 13:03:08 +0300
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> Well I think Stefan's solution is more correct and will not break anything.

I'd like to avoid any changes in behavior of kill-buffer that could
possibly affect existing code.  So if the change should be in
kill-buffer itself, please introduce an additional optional argument
that will control whether buffer visibility is considered and/or
whether the frame predicates are called; with-temp-buffer could then
use that new argument.

This function survived the last 5 years with no real changes, and even
before that most of the code which implements this logic wasn't
touched.  I see no reason to make such changes now in a very popular
function/command, for the benefit of very specialized use cases.

Thanks.



      reply	other threads:[~2017-01-18 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 19:32 kill-buffer calls frame's buffer-predicate for all buffers even if the killed buffer was not shown in any window Constantin Kulikov
2017-01-15 20:31 ` Eli Zaretskii
2017-01-16  8:14   ` Constantin Kulikov
2017-01-16 16:26     ` Eli Zaretskii
2017-01-16 16:55       ` Eli Zaretskii
2017-01-16 22:21       ` Constantin Kulikov
2017-01-17 14:26         ` Stefan Monnier
2017-01-17 14:40         ` Constantin Kulikov
2017-01-18 10:03           ` Constantin Kulikov
2017-01-18 15:43             ` Eli Zaretskii [this message]

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=83fukg8jcq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=zxnotdead@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 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.