Re: kill-buffer calls frame's buffer-predicate for all buffers even if the killed buffer was not shown in any window.

[Eli Zaretskii]

> Date: Mon, 16 Jan 2017 18:26:55 +0200
> From: Eli Zaretskii <address@hidden>
> Cc: address@hidden
> 
> So I'd suggest to leave these two commands alone, and instead
> consider adding some new function, say kill-temp-buffer, which will
> only do a small subset of what kill-buffer does, and disregard stuff
> like visibility of candidate buffers to which current-buffer needs
> to switch.

Btw, you didn't describe the use case where this issue got in your
way, so perhaps you should.  That would allow to decide whether the
problems are bad enough to look for a solution.

Thanks.