>> As noted in bug#33870 the buffer produced by xref-find-definitions
>> (bound to ‘M-.’) has a transient nature like the *Completions* buffer.
>> Therefore it makes sense not to waste its space needlessly:
>
> It doesn't make sense to review this patch until the patch that fixes 33870
> has been produced.
Since the patch from bug#33870 has been already committed,
this bug#33992 is undeadlocked now.
The problem with xref-find-definitions is its unexpected outcome:
sometimes it pops up a window, sometimes doesn't.
It's like Russian roulette: pull the trigger, bang and there is
a hole in the screen that takes the form of glaringly empty space.
I understand, but somehow I'm not very offended by that. It's just
something I've grown so used to, even before xref. Just C-h f to
a function description of which you know nothing of the length
and boom, a lot of empty space too.
While I do vaguely remember being annoyed by it many years ago,
I don't now. And for xref I like to see it well highlighted away from any
other text, so I can easily count the references. Displaying next to the
minibuffer are would surround it with more noise.
It's just the way I work. Fortunately now it is customizable, right? How about
adding an entry to the manual, in the xref section, mentioning a couple of
commands or customization variables that can be used to get the interface
that you prefer, Juri?
João