bug-gnu-emacs
[Top][All Lists]
Advanced

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

bug#23179: 25.0.92; Restore `M-,' to continue etags search


From: Eli Zaretskii
Subject: bug#23179: 25.0.92; Restore `M-,' to continue etags search
Date: Sat, 02 Apr 2016 22:58:26 +0300

> Date: Sat, 2 Apr 2016 21:46:48 +0200
> From: Anders Lindgren <address@hidden>
> Cc: address@hidden
> 
> The "xref" package is a big step forward, since it supports multiple backends 
> etc. Unfortunately, vital
> functionality is missing -- searching and query-replace in all included 
> files. Personally, I use `tags-search' at
> least 20 times per day (often more), and `tags-query-replace' several times 
> each week. I don't think that my
> use pattern is extreme by any means.

Did you try any of the alternatives suggested in this discussion?  If
none of them satisfies your needs, can you elaborate why?

> I think that we would be making a big mistake if we would release Emacs 25 
> with an "xref" without searching
> and query-replace, but with key bindings that, for most tags users, break 
> existing use patterns.

We are still discussing this issue, don't we? ;-)  And Emacs 25.1
release is still a couple of months away, so we still have time.

> > But we could have a tags-only command that presented an xref UI, I think. 
> > (Its name could be "tags-search"
> ;-)
> 
> 
> It would have been neat... Unfortunately, the problem is not launching the 
> command, but rather continue
> searching past the first match -- since a source buffer, and not the xref UI 
> buffer, will be current.

The xref UI solve this problem, as was already mentioned in this
discussion.

> I have given this some thought -- if we decide to really do make a change, 
> maybe we should try to make the
> xref search command more isearch-like, so that a user could be able to 
> continue an xref search using `C-s'
> rather than `M-,'. Unfortunately, there is no natural key binding to continue 
> a normal query replace, but we
> could create something like `xref-query-replace-from-here', to continue 
> query-replacing from the point in the
> current buffer and then continue with the next file in the file list.

xref-query-replace-in-results already provides a way for continuing
the replacement, so I'm not sure what you are had in mind here.





reply via email to

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