From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Helmut Eller Newsgroups: gmane.emacs.devel Subject: Re: Generalizing find-definition Date: Mon, 03 Nov 2014 08:03:34 +0100 Message-ID: References: <20141102151524.0d9c665c@forcix> <20141102172944.0f7944e3@forcix> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1414998269 5653 80.91.229.3 (3 Nov 2014 07:04:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Nov 2014 07:04:29 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 03 08:04:21 2014 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 1XlBgZ-0007Z2-Tr for ged-emacs-devel@m.gmane.org; Mon, 03 Nov 2014 08:04:20 +0100 Original-Received: from localhost ([::1]:60639 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlBgZ-00076Y-Fu for ged-emacs-devel@m.gmane.org; Mon, 03 Nov 2014 02:04:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlBgF-00076S-QG for emacs-devel@gnu.org; Mon, 03 Nov 2014 02:04:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XlBg8-00040o-AJ for emacs-devel@gnu.org; Mon, 03 Nov 2014 02:03:59 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:39555) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlBg8-00040k-3J for emacs-devel@gnu.org; Mon, 03 Nov 2014 02:03:52 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XlBg6-0007QN-HO for emacs-devel@gnu.org; Mon, 03 Nov 2014 08:03:50 +0100 Original-Received: from dial-181146.pool.broadband44.net ([212.46.181.146]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 Nov 2014 08:03:50 +0100 Original-Received: from eller.helmut by dial-181146.pool.broadband44.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 Nov 2014 08:03:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 43 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dial-181146.pool.broadband44.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) Cancel-Lock: sha1:Cko3C7s87RivtdmHDdubPZQRDYc= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:176249 Archived-At: On Sun, Nov 02 2014, Stefan Monnier wrote: >> In my experience, tags-loop-continue is rather hard to use and I have >> long argued to get rid of it and replace it with a better UI. >> E.g. tags-loop-continue must be pressed multiple times just to find out >> at the end that none of the offered candidates was relevant. SLIME does >> it differently: the list of all candidates is displayed in a separate >> buffer with one candidate per line; a bit like the results of a search >> engine like Google. The user must then move the cursor to the >> interesting line and press RET to actually jump to the definition. If >> there's only a single candidate, then there's no need to display the >> list and we can jump to the candidate right away. SLIME has no analog >> to tags-loop-continue (and no key binding for it) because it's not >> needed; at least nobody ever asked for such a command. > > I agree that tags-loop-continue is not super convenient. > What key-binding does SLIME use to get this list buffer (which would > most naturally be implemented as a kind of grep/compilation-mode buffer)? > Would C-u M-. be usable for that? M-. brings up the list (if there are multiple candidates; if there's a single candidate then no list is displayed). We use C-u M-. to read the symbol from the minibuffer (as opposed to parsing it from context around point). We also have a group of bindings for similar but not so important commands: C-c C-w c -- who calls (lists callers) C-c C-w w -- calls who (lists functions called by the current function) C-c C-w r -- who references (for global variables) C-c C-w s -- who sets (for global variables) C-c C-w b -- who binds (for dynamic variables) C-c C-w s -- who specializes (lists methods specialized for a specific class) C-c < -- list callers C-c > -- list callees The C-c < and C-c C-w c do conceptually the same but one is implemented with an index (like tags) and the other by scanning and inspecting function objects on the heap. Different commands for historical reasons. Helmut