From: charles@aurox.ch (Charles A. Roelli)
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 31027@debbugs.gnu.org
Subject: bug#31027: 27.0.50; xref, tags-location-ring equivalent
Date: Wed, 04 Apr 2018 20:37:32 +0200 [thread overview]
Message-ID: <m2o9iy24yb.fsf@aurox.ch> (raw)
In-Reply-To: <4540850e-1f76-22d9-cf7b-bd680eb34c6b@yandex.ru> (message from Dmitry Gutov on Tue, 3 Apr 2018 23:32:26 +0300)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 3 Apr 2018 23:32:26 +0300
>
> On 4/2/18 9:06 PM, Charles A. Roelli wrote:
> > tags-location-ring seems to have no replacement in xref.el.
> >
> > from etags.el:
> > (defvar tags-location-ring (make-ring xref-marker-ring-length)
> > "Ring of markers which are locations visited by \\[find-tag].
> > Pop back to the last location with \\[negative-argument] \\[find-tag].")
> >
> > We should add a "xref-location-ring" (or similar) that stores the
> > locations visited by "xref-find-definitions", and we can allow jumping
> > to them with C-u - M-., in the same way as "find-tag" does.
>
> What about 'M-x previous error'? Or 'C-u - M-x next-error', to mirror
> your example.
That's useful, but also different in nature and scope to a global
ring, which would not use a local variable (`next-error-function') to
navigate to other "errors". An "xref-location-ring" would be simpler.
By the way, I didn't know previous-error/next-error worked with xref.
Is that documented in the manual?
next prev parent reply other threads:[~2018-04-04 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 18:06 bug#31027: 27.0.50; xref, tags-location-ring equivalent Charles A. Roelli
2018-04-03 7:15 ` Robert Pluim
2018-04-03 17:58 ` Charles A. Roelli
2018-04-03 20:32 ` Dmitry Gutov
2018-04-04 18:37 ` Charles A. Roelli [this message]
2018-04-04 18:57 ` Dmitry Gutov
2018-04-04 19:25 ` Eli Zaretskii
2018-04-04 20:59 ` Juri Linkov
2018-04-04 22:14 ` Dmitry Gutov
2018-04-05 18:56 ` Charles A. Roelli
2018-04-05 21:05 ` Dmitry Gutov
2018-04-08 9:14 ` Charles A. Roelli
2018-04-07 20:56 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2o9iy24yb.fsf@aurox.ch \
--to=charles@aurox.ch \
--cc=31027@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).