[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tags-loop-continue

From: Dmitry Gutov
Subject: Re: tags-loop-continue
Date: Mon, 18 Jan 2016 05:57:34 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Thunderbird/43.0

On 01/18/2016 05:48 AM, Stefan Monnier wrote:

Presumably if the user uses both xref and etags-search, then she knows
about both meanings of M-, and she should hence "intuitively"
understand that there's a conflict.

Sure she does.

For that specific case, we could let the user use C-u M-, in order to
specify which of the two commands to use.

Or, you know, she could just use M-x tags-loop-continue for tags-loop-continue.

Admittedly, I'm not sure this assumption that "the user will intuitively
know that there's a conflict" holds.


Maybe we'd be better off keeping M-, for tags-loop-continue for now and
use M-* for xref-pop-marker-stack.  It at least has the benefit of
reducing the differences between 24.5 and 25.1.
So it can be seen as an intermediate step and in 26.1 we could get rid
of tags-loop-continue (assuming we figure out how) and move
xref-pop-marker-stack to M-,

If, to be rid of tags-loop-continue, implementing the two Dired commands to use the xref UI is enough, I'll have that soon.

Otherwise, why put ourselves in an inconsistent state (and force users to re-learn keys twice)? If we're so worried about backward compatibility, let's rip out all new xref bindings and on-obsolete all corresponding etags commands.

The interested users would enable some xref-bindings-mode we can add without much fuss. The rest will continue to live undisturbed.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]