Re: next-error-last-buffer

[Juri Linkov]

Ted Zlatanov <address@hidden> writes:
> What predefined behaviors should we allow?
>
> - use the last visited buffer
> - prefer {compile,grep,occur} buffers
> - use the visible buffers
> - user-defined function
>
> The behavior preferences should be in a list, so the user can say "use
> my function, then use the visible buffers first, then try a compile
> buffer, then use the last visited buffer" for instance.  I really
> think most users will be happy with a default of "last visited buffer"
> but we should let the users decide by making it easy to configure.

Defining rules by a list would be good.  For example:

(defcustom next-error-find-buffer-functions
  '(next-error-visible-buffer         ; predefined function
    next-error-find-buffer-function   ; user-defined
    next-error-last-buffer            ; predefined function
    ...)
  :type '(repeat symbol))

But isn't this unnecessarily complicated?

>> 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.
>
> You are not a typical user.  I, for instance, have NEVER run more than
> one compilation at a time.  I may have to in the future, sure, but I
> doubt it's typical user behavior.

So we are free to define any default behavior of selecting the compilation
buffer because any our decision will not affect typical users ;-)

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