Re: next-error-last-buffer

[Richard Stallman <rms@gnu.org>]

    1. Add an option to allow the user to select among predefined
    behaviors.  Though, this will not help the user if he will not
    find a desired option in the predefined set.

I don't want to offer the user a choice of several behaviors
that are all unsatisfactory in various ways.  This way lies
lots of complexity without really satisfying anyone.

What we should do, when we see how, is make the default behavior
better.

    2. Add a new user variable `next-error-find-buffer-function' and try
    to call it (i.e. to call it if it's fbound and return its value,
    but if it returns `nil', try other rules) in `next-error-find-buffer'
    at the top precedence level before all other rules.

Is this really an improvement?  It is not that hard for users
who want different behavior to edit the code.

    I thought again about why the current behavior is too confusing
    and I think I found the reason: the most confusing is the fact that
    the compilation buffer is visible in the window adjacent to the
    source file window where the point is located, but typing C-x `
    uses the last but not visible compilation buffer.

Perhaps next-error should always choose a compilation or occur buffer
that is visible in a window, rather than one that isn't.  And it
should prefer one that is visible in the current frame to one that is
visible in another frame.  This might help us get a better default
behavior.