From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] emacs-25 f8208b6: Document the user-level features of the Xref package Date: Fri, 22 Jan 2016 00:40:36 +0300 Message-ID: <56A15054.20304@yandex.ru> 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> <831t9a8yik.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1453412468 12078 80.91.229.3 (21 Jan 2016 21:41:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Jan 2016 21:41:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 21 22:41:07 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 1aMMyZ-0004bc-9q for ged-emacs-devel@m.gmane.org; Thu, 21 Jan 2016 22:41:07 +0100 Original-Received: from localhost ([::1]:49809 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMMyY-0000e8-LO for ged-emacs-devel@m.gmane.org; Thu, 21 Jan 2016 16:41:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMMyB-0000Zb-8L for emacs-devel@gnu.org; Thu, 21 Jan 2016 16:40:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMMy8-0007EB-28 for emacs-devel@gnu.org; Thu, 21 Jan 2016 16:40:43 -0500 Original-Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:34751) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMMy7-0007E2-Qu; Thu, 21 Jan 2016 16:40:40 -0500 Original-Received: by mail-lf0-x236.google.com with SMTP id 17so35428100lfz.1; Thu, 21 Jan 2016 13:40:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=GO4SDk/s0GNu1nahv/jnafh/GqhDpVvo0fQ/fzdRKWc=; b=FjFz6OOSJX3exMc8ee7XSLHhaa5JS+clalHln+yl8m+NmtXukUgVNa7fyhddOu5DLl Owf9FMG07Z0rvau9w3zmJVzgDmUOXii5sFOZutpr495KFi7lR4gpOsGM1sdEgvDRaX7I pTOfe2Ou1xnRa6eBSaTO07WT613TI1RGSvYwkEupGCpvUbh9i5l9yjCp1g9L0KLDyG0i 52nJxv+n4YMA25IsX6ox1hPa19Tlm8MPhAI9kjXcfRFuy+voCHn+G4ukhE/AU7buDiGC DlFf7wesHBhumdF5XPRTRyXUyt+zd5Gwo3QbfWzZYB11W2rf5sgWFq4J3sCfT9b6rCRv Of/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=GO4SDk/s0GNu1nahv/jnafh/GqhDpVvo0fQ/fzdRKWc=; b=hEoD7T7nWffE2oPBdG3XUZTECdLA0B4eZ8EAR2q/HNJvA6MZPWd2zCNi0MI3R2VPp6 4CycbTg2lFA2KFMwl81RT65XkTtKFmTPJTLP98s28B13CQvNmG6/FG6kqjMhIMtdPTg6 TCNeEAEKg/LXScpWpZCqJX2omAsNTZthSveGRF6bHJ12vLaGgarZIDVYgsnewo/fBgOU y7XJ5+KtPt0q9Bpu80x/QL9d7olenmjMZ/pWXzXnLdkZ/pj77I0YirI2rr4HlFDwKqQ2 ZEqMpmhjmS8QfypjECkcQIkaOpMgl4zPJEG2CtWxftDBg2kBBWE8d1NJOubj7BarWPdC MEzg== X-Gm-Message-State: ALoCoQlBTRNgdl96LwHw2ejY/Yk0Tty3f96yX1+vWyArQNrs1uzWKTk+PT7IaDjcP4uQGSOm7pGX2HqE8VTETwQ5hEdzpfKIDg== X-Received: by 10.25.32.75 with SMTP id g72mr13518123lfg.110.1453412438898; Thu, 21 Jan 2016 13:40:38 -0800 (PST) Original-Received: from [192.168.1.190] ([178.252.127.222]) by smtp.googlemail.com with ESMTPSA id xf10sm457882lbb.23.2016.01.21.13.40.37 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Jan 2016 13:40:38 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Thunderbird/44.0 In-Reply-To: <831t9a8yik.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c07::236 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:198538 Archived-At: On 01/21/2016 11:32 PM, Eli Zaretskii wrote: >> 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. We wouldn't want to use a command that searches an arbitrary set of files, which depends only on the mood of the person who wrote a particular backend. Stricter semantics are needed. Furhermore, Dired's commands we're replacing had default bindings. tags-search only has a menu entry. >> 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. That doesn't look general enough. What do I write in the docstring? "Searches where the TAGS files tell it to, or does similar stuff"? >> 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. We should wait for more opinions, then. It won't be hard to add a command like that later.