bug#47050: 28.0.50; [PATCH] `next-error-find-buffer' does things in the wrong order

[Juri Linkov]

> The doc for `next-error' says:
> ...
> I interpreted that to mean that if I create e.g. two `grep' buffers and
> rename them uniquely to `*grep*<2>' and `*grep<3>', then switching
> to one or the other of them and calling `next-error' would use the hits
> from that buffer. However it always uses the hits from the last-used grep
> buffer and I have to change that explicitly, by calling
> `next-error-select-buffer', instead of letting the current buffer
> determine it.

Please try to customize 'next-error-find-buffer-function' to this value:

  (const :tag "Current buffer if next-error capable and outside navigation"
         next-error-buffer-unnavigated-current)

It provides the behavior that you described.