bug#6454: 24.0.50; kill-buffer switches current-buffer

[martin rudalics]

> I'm wondering a bit though: kill-buffer protects the current buffer
> while calling kill-buffer-hook.  Wouldn't it be prudent to do that for
> the entire function?

You mean for the case where the buffer we want to kill is not the
current buffer?

> Actually, I think there is a small bug there: if kill-buffer-hook is a
> list of functions, the first function could potentially switch buffer
> and the second function would be called in the wrong buffer.

I suppose you're right.  Could you propose a patch for this and the
above issue?

> [The change in window_loop looks like good thing either way.]

`delete-windows-on' has the same problem.

martin