unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: unifying emacs "go to definition" functionality
Date: Wed, 20 Feb 2013 07:59:06 +0100	[thread overview]
Message-ID: <5124743A.2040404@online.de> (raw)
In-Reply-To: <CADOO-JyPRaXWLvh0U3XE+H2pQbO8dbEOqL1CKw7mRs5j_1nRoQ@mail.gmail.com>

Am 20.02.2013 01:28, schrieb Brendan Miller:
> Right now emacs has several modules that offer "go to definition"
> functionality, all of which have different implementations, and
> different behavior.
>
> 1. Etags uses M-. and M-* to push and pop from a pair of tag stacks
> (find-tag-marker-ring, and tags-location-ring).
>
> 2. elisp uses C-h f TAB RETURN to jump to definition. It has no tag
> stack, so there's no way to jump back.
>
> 3. CEDET uses C-c , J to jump to definition. It has no tag stack,
> though it pushes to the global mark ring.
>
> 4. Jedi (jump to definition/autocompletion for python) uses C-. It has
> no tag stack.
>
> 5. SLIME uses etags keybindings, but I don't think it uses etags stack.
>
> By far the etags interface (M-. to jump to definition and push the
> location, M-* to pop back), is the easiest interface to use, though
> the underlying tagging engine is less precise than the others.
>
> My suggestion is that the etags key bindings and tag stack be made
> generic, and that M-. trigger some kind of callback through a buffer
> local variable, so that jump to definition can be handled in a mode
> specific way.
>
> Note that in addition to reusing the same keybindings, reusing the
> same tag stack gives that added benefits that it's possible to
> navigate through a high level language into a lower level language,
> and then pop back out with M-*. I have this mocked up (in kind of a
> hacky way) with elisp and C, where I can jump from elisp into the C
> definition of a native function, navigate around C with etags or
> CEDET, and then pop back out back into elisp again.
>
> I'd be interested in taking a look at the implementation work behind
> this in the future, but initially I just wanted to put the idea out
> there for feedback.
>
> Brendan Miller
>
>

Are backsides of etags:

need to run in advance, hard to follow when changing Emacs version

My favourite is a solution based on

find-function-noselect

http://repo.or.cz/w/elbb.git/blob/HEAD:/code/Go-to-Emacs-Lisp-Definition.el

Andreas



  parent reply	other threads:[~2013-02-20  6:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20  0:28 unifying emacs "go to definition" functionality Brendan Miller
2013-02-20  3:00 ` Stefan Monnier
2013-02-20  4:54 ` Dmitry Gutov
2013-02-20  6:59 ` Andreas Röhler [this message]
2013-02-20 13:44   ` Dmitry Gutov
2013-02-20  8:52 ` Helmut Eller
2013-02-20  9:07   ` Andreas Schwab
2013-02-20  9:28     ` Helmut Eller
2013-02-20  9:36       ` Andreas Schwab
2013-02-20  9:45         ` Helmut Eller
2013-02-20 13:51         ` Stefan Monnier
2013-02-20  9:59   ` Lawrence Mitchell
2013-02-20 10:21     ` Jambunathan K
2013-02-20 10:40       ` Jambunathan K
2013-02-20 15:21     ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5124743A.2040404@online.de \
    --to=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).