From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
yyoncho <yyoncho@gmail.com>,
38797@debbugs.gnu.org
Subject: bug#38797: 27.0.50; Feature request: provide the opposite of xref-pop-marker-stack
Date: Mon, 25 Oct 2021 10:44:01 +0300 [thread overview]
Message-ID: <877de1lfb2.fsf@mail.linkov.net> (raw)
In-Reply-To: <4c25c196-ba72-b509-c5d7-f015c37009f8@yandex.ru> (Dmitry Gutov's message of "Mon, 25 Oct 2021 02:22:06 +0300")
>>> That reminds me of a potential feature: saving the history of searches and
>>> going back/forward between them, in the manner of help-go-back and
>>> help-go-forward (maybe even with same keybindings).
>>>
>>> From that perspective, we could choose the names in advance. Either
>>>
>>> xref-go-back/forward and xref-history-back/forward
>>>
>>> or, I suppose
>>>
>>> xref-back-history/forward-history and xref-searches-back/forward
>>>
>>> ...something like that.
>> I never had such a problem thanks to the customization
>> that creates a new buffer for every search:
>> (add-hook 'xref--xref-buffer-mode-hook 'rename-uniquely)
>
> It's a nice intermediate solution, but it would also be nice to be able to
> quickly iterate across previous searches. No?
This means adding another layer of complexity. Remember a mess
of deciding how to switch next-error navigations from different searches?
Switching multiple xref searches will have the same level of confusion.
BTW, shouldn't xref-go-back/forward support next-error-function? ;-)
next prev parent reply other threads:[~2021-10-25 7:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 18:11 bug#38797: 27.0.50; Feature request: provide the opposite of xref-pop-marker-stack yyoncho
2020-01-23 14:13 ` Dmitry Gutov
2021-10-20 19:12 ` Mattias Engdegård
2021-10-24 1:40 ` Dmitry Gutov
2021-10-24 7:54 ` Juri Linkov
2021-10-24 12:39 ` Dmitry Gutov
2021-10-24 19:10 ` Juri Linkov
2021-10-24 23:22 ` Dmitry Gutov
2021-10-25 7:44 ` Juri Linkov [this message]
2021-10-25 15:18 ` Dmitry Gutov
2021-10-25 17:07 ` Juri Linkov
2021-10-24 13:24 ` Mattias Engdegård
2021-10-25 2:13 ` Dmitry Gutov
2021-10-25 15:49 ` Mattias Engdegård
2021-10-25 17:05 ` Juri Linkov
2021-10-25 18:53 ` Mattias Engdegård
2021-10-25 19:38 ` Dmitry Gutov
2021-10-25 21:29 ` Glenn Morris
2021-10-26 8:06 ` Mattias Engdegård
2021-11-08 18:23 ` Juri Linkov
2021-11-09 8:30 ` Juri Linkov
2021-11-09 13:08 ` Mattias Engdegård
2021-11-09 13:09 ` Dmitry Gutov
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=877de1lfb2.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=38797@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mattiase@acm.org \
--cc=yyoncho@gmail.com \
/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).