Re: xref and displaying locations in appropriate window or frame

[Dmitry Gutov]

On 01/24/2016 08:58 PM, Eli Zaretskii wrote:

> With RET, yes.  But this doesn't happen with '.'.  Isn't that
> confusing?

Somewhat, yes. But it avoided the problem of showing a buffer while 
avoiding touching two windows.

> RET runs xref-goto-xref, so whatever RET does, xref-goto-xref will do
> the same, no?

Yes. Including hiding the xref buffer, like currently implemented.

> As for xref-show-location-at-point, it doesn't bury the *xref* buffer
> when I try it now, so it looks like it already avoids hiding *xref*.

Avoids, yes. And it doesn't fulfill the "show in this/other 
window/frame" contract, like you've observed.

It's possible that we can easily have only one or the other.

> I have a terrible feeling that I'm missing something important here.

Not sure if you are.

> > I only mean that the original buffer will be hidden, and the user won't
> > be able to look at its contents while making the choice. Which might be
> > considered bad, for the default behavior. Maybe not too terrible, though.
>
> No, I don't think it's terrible.  There's always
> xref-pop-marker-stack, right?

I suppose.