RE: Buffer listing in multiple frames/ttys

["Drew Adams" <drew.adams@oracle.com>]

    The following definitions change `prev-buffer' and `next-buffer' to
    follow the frame-local buffer ordering instead of the global
    `buffer-list'.
    
    Now, I like these definitions as it makes more sense for me to keep
    the buffer cycle frame-local, but they do have one disadvantage: the
    `next-buffer'/`prev-buffer' cycle will not usually contain all
    buffers---just those that were displayed in the current frame.  To
    reach the rest, the user needs to use `switch-to-buffer', or
    equivalent.
    
I may have misunderstood (I have not been following the latest part of this thread closely), but IIUC this would, for the same reasons discussed earlier, be inappropriate for many of us who use pop-up-frames = t. 

I don't really care, for myself, as I am unlikely to use next-buffer/prev-buffer, but I think it could be important for others who do want to use those commands with the one-buffer-per-frame-by-default behavior of pop-up-frames = t.