all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: xref window switching problems
Date: Wed, 05 Aug 2015 01:56:00 -0500	[thread overview]
Message-ID: <86a8u6cjgf.fsf@stephe-leake.org> (raw)
In-Reply-To: <87bnemn8mk.fsf@acer.localhost.com> (Ingo Lohmar's message of "Tue, 04 Aug 2015 21:42:11 +0200")

Ingo Lohmar <i.lohmar@gmail.com> writes:

> The behavior is perfectly understandable looking at the code of
> xref--pop-to-location and xref--goto-location, but is this intended?

I can't speak to whether it's intended, but I agree it's not good.

> The old pre-xref elisp implementations and the tags functions got the
> "...-other-window" behavior right IMO: Leave my current window's buffer
> and point alone in any case, and pop to the target shown in another
> window.

+1

> The change would be easy (see xref--pop-to-location), first get the
> buffer, then do the window business, and only then xref--goto-location.
>
> Any objections/opinions?  

Sounds good to me

> Maybe xref-pop-marker-stack could benefit from a discussion as
> well.

I haven't used that much, but so far it does what I want; change the
current window to display the previous location.

If I want to preserve the current location in a window, I would first
move to a different window; I haven't tested to see if that works in the
one buffer/two locations scenario.

-- 
-- Stephe



  reply	other threads:[~2015-08-05  6:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 19:42 xref window switching problems Ingo Lohmar
2015-08-05  6:56 ` Stephen Leake [this message]
2015-08-05 12:40   ` Dmitry Gutov
2015-08-06  9:16     ` Stephen Leake
2015-08-05 12:33 ` Dmitry Gutov
2015-08-05 20:30   ` Ingo Lohmar
2015-08-06  7:05     ` Dmitry Gutov
2015-08-06  9:36     ` Stephen Leake
2015-08-07 17:25       ` Ingo Lohmar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86a8u6cjgf.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.