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:02:39 +0200 Message-ID: <8360ym8zvk.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> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453406567 12597 80.91.229.3 (21 Jan 2016 20:02:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Jan 2016 20:02:47 +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:02:41 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 1aMLRJ-0000SE-F1 for ged-emacs-devel@m.gmane.org; Thu, 21 Jan 2016 21:02:41 +0100 Original-Received: from localhost ([::1]:49572 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMLRI-0000yq-FL for ged-emacs-devel@m.gmane.org; Thu, 21 Jan 2016 15:02:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMLR6-0000xt-5d for emacs-devel@gnu.org; Thu, 21 Jan 2016 15:02:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMLR2-0000Gk-Vi for emacs-devel@gnu.org; Thu, 21 Jan 2016 15:02:28 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:51643) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMLR2-0000Ge-Sb; Thu, 21 Jan 2016 15:02:24 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4557 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aMLR1-0003c2-Vv; Thu, 21 Jan 2016 15:02:24 -0500 In-reply-to: <56A1357B.2020601@yandex.ru> (message from Dmitry Gutov on Thu, 21 Jan 2016 22:46:03 +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:198529 Archived-At: > Cc: emacs-devel@gnu.org > From: Dmitry Gutov > Date: Thu, 21 Jan 2016 22:46:03 +0300 > > On 01/21/2016 10:00 PM, Eli Zaretskii wrote: > > > But a reference includes a file name, doesn't it? If so, why not > > search through those files? > > My core objection is that "find regexp" is not a semantic query. Whereas > all current xref queries are semantic (i.e. require language analysis > for best results). > > 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. > >> 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. > > It would be OK for xref-find-regexp to do the same. Users who want > > the project.el way of doing that can invoke the commands there. (They > > should probably be documented in the manual.) > > We should worry that a user might invoke xref-find-regexp while > expecting it to behave like project-find-regexp. I don't. > Because in most other editors regexp search works more like the latter: > it's either in the current file, or across the current project. I'm not lobbying for supplanting the project.el command. It has its uses.