Re: Window configurations

[martin rudalics]

>> So we have to decide
>>
>> (1) wherever this "But it should put ..." shall be done (in
>>     `bury-buffer', `quit-window', ...), and
>
> I suppose this should be done in all places that currently modify
> the buffer-list.

`select-window' does modify the buffer list but there we probably don't
care.  Anyway, what I need to know is how to deal with all the
`other-buffer' calls in general.  For example, how do we determine the
prompt for `read-buffer-to-switch'?  This is called by
`switch-to-buffer' but also by `switch-to-buffer-other-window' and
`switch-to-buffer-other-frame' where we don't know the target window in
advance.  And we certainly don't want to prompt with a visible buffer
there.

>> (2) whether a window-local buffer-list may contain something else but
>>     entries associated with buffers (as your text somehow insinuates).
>
> Yes, elements of a window-local buffer-list should also contain
> window-start and window-point.

In my `quit-restore-window' parameter I currently store whether to the
kill the window and which window to select instead.  These are not very
compatible with buffer lists but I do need them in order to keep up the
current behavior of quitting a help buffer or view mode.  Mixing these
into window local buffer list is not very nice.

martin