Re: Window configurations

[martin rudalics]

>>> I think changing the argument VISIBLE_OK won't help.  The existing
>>> calls of `other-buffer' (where VISIBLE_OK is nil) should keep the
>>> current behavior of `other-buffer' that prefers not visible buffers
>>> to visible buffers (when the window-local buffer-list is empty).
>> You mean that when the window-local buffer-list is not empty these calls
>> should be allowed to choose a visible buffer?  What if an application
>> wants to specify for a specific call that `other-buffer' does not return
>> a visible buffer?
>
> Then `other-buffer' is too low-level to implement this.
> Maybe `kill-buffer' and `bury-buffer' are more suitable places.

We could use a 'this-window-only value for the VISIBLE_OK argument.

> I don't see a problem with `split-window': after splitting, the second
> window's buffer-list is empty, thus it adheres to the current behavior.

I meant after splitting _and_ selecting the new window in order to
decide which buffer to display in it.  I suppose we always want to
update the window-local buffer list after selecting a window with
NORECORD nil?

martin