Re: Buffer listing in multiple frames/ttys

[Juri Linkov]

>> The current implementation of `buffer-list' frame parameter doesn't
>> preserve the correct ordering of buffers selected in the same frame.
>>
>> After using `next-window' in one frame, `previous-window' in another
>> frame gets the buffer buried in the first frame, but not in the
>> same frame where it is called.
>>
>> Since two commands `next-window' and `previous-window' make a ring
>> from the buffer list, this ring becomes broken when used in two or
>> more frames.
>
> I think you mean `next-buffer' and `prev-buffer' here, no?

This is exactly what I meant.  Sorry for being so distrait.

> Does this patch fix it?

Not at all.  The problem is that `bury-buffer' (called from `next-buffer')
removes the buffer from the frame's buffer-list.  So a buried buffer is
no longer available from (frame-parameter nil 'buffer-list) for
`prev-buffer' called in the same frame after changing the order of
buried buffers in another frame.

Perhaps, there should be a separate list of buried buffers maintained
in a new frame parameter.

-- 
Juri Linkov
http://www.jurta.org/emacs/