bug#33870: 27.0.50; xref-goto-xref not configurable

[Juri Linkov]

>> Then suddenly M-. replaces other half of the screen with empty space with
>> only 2 lines at the top.  This is because there is an ambiguity in finding
>> definitions, and you need to resolve it.  Then you start trying to reuse some
>> empty space it creates and trying to split the xref window.  Instead of
>> this, the split is applied to the original window.
>
> Could you write down the commands to get there? I failed to reproduce this.

Any command that relies on configuration in display-buffer-alist
or display-buffer-overriding-action such as windmove-display-in-direction.

>> Now the question is what to do when the user asks to display
>> a definition in another window using ‘C-x 4 .’
>> (xref-find-definitions-other-window).  The most natural way is to
>> immediately take the window pointed out by the user configuration
>> (the user can configure to display it below/above/left/right etc.)
>> and display the xref window in that window.
>
> I'm not sure if it's the "most natural" way. "A natural" maybe.

At least, the current behavior can't be described as "natural".
For example, if the user prefers using frames and types `C-x 5 .'
the xref buffer is displayed in another WINDOW, not FRAME.