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-find-matches and stuff Date: Mon, 4 May 2015 15:39:00 +0300 Message-ID: <55476864.90900@yandex.ru> References: <5546DD4A.2080709@yandex.ru> 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 1430743183 29020 80.91.229.3 (4 May 2015 12:39:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 May 2015 12:39:43 +0000 (UTC) Cc: emacs-devel To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 04 14:39:37 2015 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 1YpFeq-00059Z-Q4 for ged-emacs-devel@m.gmane.org; Mon, 04 May 2015 14:39:36 +0200 Original-Received: from localhost ([::1]:34062 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpFep-00025z-VI for ged-emacs-devel@m.gmane.org; Mon, 04 May 2015 08:39:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47292) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpFeZ-00025o-9z for emacs-devel@gnu.org; Mon, 04 May 2015 08:39:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YpFeW-0003jQ-6F for emacs-devel@gnu.org; Mon, 04 May 2015 08:39:19 -0400 Original-Received: from mail-wg0-x232.google.com ([2a00:1450:400c:c00::232]:35330) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpFeV-0003bT-P7 for emacs-devel@gnu.org; Mon, 04 May 2015 08:39:15 -0400 Original-Received: by wgyo15 with SMTP id o15so148669053wgy.2 for ; Mon, 04 May 2015 05:39:05 -0700 (PDT) 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=1NrngXf+yhlqPKBQLI69JHSMz0uNmqO49VrAFiAbcGc=; b=f3eiQJEf5aZusHx8WDw8k2zh1clFpbtH4yLA8jFS094tRMsGN8Bpw6fd86y85EEGDf FIoS0VCIzSOGc1jZamcssKr06C7S2fvW87BPt7CJ0UfZVjF7r2Bc3U5keWiiQp+8Erm7 XjkVAvRUmitj7pMyyl0mpxM9yCHwaTRaSjT1Fiyux+p9v3fSgL1gq/FkCrE9z+rrAANm hWtH3WSQ8DXviTIvet5XkqF49789A2uYZKnxJmOY4DSAV4LpMzlG88XvBvWKwQSKU9W5 cP5rjl6ddehuQVmFOnZMQ27eROEzpXrJ5RRgwBs/gaGRsB0IO2cY/5aGHuUInPcqx7zI +9XQ== X-Received: by 10.194.95.41 with SMTP id dh9mr42005692wjb.55.1430743145748; Mon, 04 May 2015 05:39:05 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id fa8sm11041886wib.14.2015.05.04.05.39.04 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 May 2015 05:39:05 -0700 (PDT) user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 in-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::232 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:186180 Archived-At: On 05/04/2015 12:17 PM, Helmut Eller wrote: > With a separate xref-find-matches command it would make sense for > xref-find-apropos to work more like the normal apropos, with doc-strings > and such. They still have different purposes, but sure, we can make an xref-with-doc element or something, which would render itself with a docstring. > Ideally use the same UI as Elisp's apropos. That might be more complicated: a) the element would need to be specialized for the elisp backend, with type and plist, b) pressing RET in M-x apropos output does not get you to the symbol's definition; instead you jump between various Help buffers. I don't know if we want that for xref-find-apropos, that's certainly hard to generalize across languages. > If we're going to modify something then location info better be super > accurate. The "search and replace" interface would have to be something like M-x tags-query-replace, at least at first. It's using a regexp, so people are probably used to confirming each replacement.