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: xref-query-replace Date: Sat, 9 Jan 2016 23:46:21 +0300 Message-ID: <5691719D.4030308@yandex.ru> References: <8360z2ojqd.fsf@gnu.org> <56912C28.8010002@yandex.ru> <831t9qogl8.fsf@gnu.org> <569139D1.5040907@yandex.ru> <83y4byn0jx.fsf@gnu.org> <56916801.4040907@yandex.ru> <83twmmms49.fsf@gnu.org> <56916BEB.3040705@yandex.ru> <83r3hqmrap.fsf@gnu.org> <56916F25.9090403@yandex.ru> <83poxamqpb.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 1452372409 3839 80.91.229.3 (9 Jan 2016 20:46:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Jan 2016 20:46:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 09 21:46:43 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 1aI0PK-0001EZ-RO for ged-emacs-devel@m.gmane.org; Sat, 09 Jan 2016 21:46:42 +0100 Original-Received: from localhost ([::1]:42917 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI0PK-0005eK-0X for ged-emacs-devel@m.gmane.org; Sat, 09 Jan 2016 15:46:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47814) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI0P5-0005e4-4K for emacs-devel@gnu.org; Sat, 09 Jan 2016 15:46:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aI0P1-0000cb-Pb for emacs-devel@gnu.org; Sat, 09 Jan 2016 15:46:27 -0500 Original-Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:36641) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI0P1-0000cW-IK; Sat, 09 Jan 2016 15:46:23 -0500 Original-Received: by mail-lf0-x236.google.com with SMTP id i124so27122708lfe.3; Sat, 09 Jan 2016 12:46:23 -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=csIe+qHL9F5jfx2sQvn/QzGfvFJdLztBCwhNim3zE/Q=; b=z4oAEGRCSU1jtg/za3uJFwMOmEEoc8DKMl5mGJL3/xwj+i0d5ZE64aw15R0dGm4CPz dEP9hPDLxiCf3Etb5D3QnGiQ/ba7Fuyu+1kGtbLGDaINKuOvqbuXrqOT5FMm6QWN3pZI iWtx76sUgFt2mjJj+3ENvxmWZWkDog3muBmUJH/q+uUApRLGThi8T6bsJ2uj+Fv9Qmk+ CVDW/g5J+bQWKTrEwwle4+CYrqgi578eOrfL5iQhlLRsRNszuAxEHHy939/6wj+M8Kjv DUkv3+lE9eytL6YFbIABDHlcoFW4/zqvQbfX4OOv7ingwQ4q5gRWjViPVh4kCz0aBN/q aa1w== X-Received: by 10.25.39.200 with SMTP id n191mr42780562lfn.7.1452372382695; Sat, 09 Jan 2016 12:46:22 -0800 (PST) Original-Received: from [192.168.1.190] ([178.252.127.222]) by smtp.googlemail.com with ESMTPSA id xo4sm14949569lbb.27.2016.01.09.12.46.21 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Jan 2016 12:46:21 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Thunderbird/43.0 In-Reply-To: <83poxamqpb.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:197929 Archived-At: On 01/09/2016 11:40 PM, Eli Zaretskii wrote: > I don't really understand why. If you have a set of matches for a C++ method A::C#foo, what value should xref-match-length return for each of them? Can you tell that value in advance, just based on the method's qualified name? > But if you insist, the only way to > explain this is to explicitly mention all the commands that produce > "good" XREF buffers in the error message. Yes, it will be a long > one. But that's not a catastrophe. Technically, this list is an open one: anyone can call xref--show-xrefs with a list of appropriate values. This function, or one like it, should be public in some next release. If we define a collective term for such xref functions, we could mention it in their docstrings.