GNU bug report logs - #38797
27.0.50; Feature request: provide the opposite of xref-pop-marker-stack

Previous Next

Full log

Message #37 received at 38797 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: Mattias Engdegård <mattiase <at> acm.org>,
 yyoncho <yyoncho <at> gmail.com>, 38797 <at> debbugs.gnu.org
Subject: Re: bug#38797: 27.0.50; Feature request: provide the opposite of
 xref-pop-marker-stack
Date: Mon, 25 Oct 2021 10:44:01 +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?  ;-)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.