From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] emacs-25 f8208b6: Document the user-level features of the Xref package Date: Thu, 21 Jan 2016 22:32:03 +0200 Message-ID: <831t9a8yik.fsf@gnu.org> References: <20160109191428.26341.44105@vcs.savannah.gnu.org> <5691C9D2.7080905@yandex.ru> <83egdpmo1j.fsf@gnu.org> <56929D6F.2050508@yandex.ru> <834melmfa4.fsf@gnu.org> <5692B1E0.8010100@yandex.ru> <831t9pma4e.fsf@gnu.org> <5693FDFA.2070607@yandex.ru> <83ziwbkj5l.fsf@gnu.org> <5694055E.6050201@yandex.ru> <83si1udcaz.fsf@gnu.org> <569D64AC.1060606@yandex.ru> <83powxbh6c.fsf@gnu.org> <569EB04F.800@yandex.ru> <8337tsc133.fsf@gnu.org> <56A05073.5090100@yandex.ru> <83powu96yo.fsf@gnu.org> <56A1277B.9080001@yandex.ru> <83a8ny92rg.fsf@gnu.org> <56A1357B.2020601@yandex.ru> <8360ym8zvk.fsf@gnu.org> <56A13B4C.6040101@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453408329 9605 80.91.229.3 (21 Jan 2016 20:32:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Jan 2016 20:32:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 21 21:32:05 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aMLtk-0006FH-Em for ged-emacs-devel@m.gmane.org; Thu, 21 Jan 2016 21:32:04 +0100 Original-Received: from localhost ([::1]:49641 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMLtg-00082h-PA for ged-emacs-devel@m.gmane.org; Thu, 21 Jan 2016 15:32:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46853) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMLtc-000824-Gp for emacs-devel@gnu.org; Thu, 21 Jan 2016 15:31:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMLtZ-0007gs-Ax for emacs-devel@gnu.org; Thu, 21 Jan 2016 15:31:56 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52085) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMLtV-0007gZ-I4; Thu, 21 Jan 2016 15:31:53 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4585 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aMLtU-0003IA-G2; Thu, 21 Jan 2016 15:31:49 -0500 In-reply-to: <56A13B4C.6040101@yandex.ru> (message from Dmitry Gutov on Thu, 21 Jan 2016 23:10:52 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198533 Archived-At: > Cc: emacs-devel@gnu.org > From: Dmitry Gutov > Date: Thu, 21 Jan 2016 23:10:52 +0300 > > On 01/21/2016 11:02 PM, Eli Zaretskii wrote: > > >> So really want some clear justification, rather than "etags has command > >> that does this", and "a user could want this". Without the > >> justification, it would be hard to document the new command anyway. > > > > Same justification as for Dired's command you just coded. Except that > > in this case, I want to search and/or replace in files that belong to > > some coherent group that is not a directory hierarchy. > > Dired's command makes sense: when there's no project, or we want to > search some dirs specifically, we can fire up Dired, select the > directories and files one by one, and do the search. The same with a backend: it selects the files to search. > When you call xref-find-regexp, you won't get to tell exactly what you > want. So, the command needs to have some useful, clear semantics. It does. With the etags backend, the TAGS file tells it to, and the user controls what goes into that file. I presume other backends could do similar stuff. > >>>> How about xref-query-replace-in-matches? > >>> > >>> Fine with me. > >> > >> You'd agree that tags-query-replace doesn't require a direct replacement > >> then? > > > > I thought that was what xref-query-replace-in-matches will do. > > xref-query-replace-in-matches will be the new name for the current > xref-query-replace. The changed name should signify that it replaces, > indeed, in the already-present list of matches. > > Since you said that having xref-query-replace called almost the same as > tags-query-replace is confusing. Ah, okay. That'd be good, but we still should try to find a good xref replacement for tags-query-replace, IMO.