Drew Adams <drew.adams@oracle.com> writes:
> The default ordering is chronological, so, yes, the most recent
> buffer is always first. The relative order of the other buffers is
> not changed, however (currently).
>
> Your reordering goes beyond that - the change in order is confusing,
> unless one is thinking in terms of multiple buffers per frame and
> one knows about the new behavior. 

Well, if there is any change in the relative order, then that implies
that the frames sometimes change what buffer they display.  The
`buffer-list' frame parameter contains a chronological list of buffers
that were ever displayed in the frame.  The new code will not change
the relative order of buffers in *Buffer List* unless this list has
more than one entry.  But that would imply that the user does use
multiple buffers per frame, so arguably the new code can be useful.
How about that! :-)

I think we have spent too much time on this.  I agree that there is no
point in having frame-local buffer lists when pop-up-frames is set to
t, so I propose in that case we continue to use the global
buffer-list, as before.  However, the frame-local version does have
important benefits for the "thematic frame" people and when there are
multiple terminals, so let's keep it enabled when pop-up-frames is not
set.

> That means that the new behavior would need to be documented
> explicitly, or else people will not understand what they see.

I will do that, of course.

> Given that, I can't say I'm annoyed by your change. I was thinking
> of the (imagined) need to re-sort.

So, should I apply this patch or not? :-)