unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lawrence Mitchell <wence@gmx.li>
To: emacs-devel@gnu.org
Subject: Re: unifying emacs "go to definition" functionality
Date: Wed, 20 Feb 2013 09:59:02 +0000	[thread overview]
Message-ID: <87vc9n8fx5.fsf@gmx.li> (raw)
In-Reply-To: m2ehgbz7t5.fsf@gmail.com

Helmut Eller wrote:

[...]

> Using the etags stack is pretty easy.  A more difficult problem is how
> to deal with names that have multiple definitions or definitions that
> have multiple source locations.  E.g. in Emacs Lisp a variable and a
> function can have the same name or in C a function can have a prototype
> definition in a .h file and the actual definition is a .c file.  This
> problem is especially important with languages that have multiple
> methods with the same name.

> In SLIME, when a name has multiple definitions we display all
> definitions (one per line with some context) in a special buffer and the
> user must then choose which one he wants (the next/previous-line
> commands in that buffer automatically displays the source of the current
> definition in the other buffer).

FWIW this is what I do for multiple generic interfaces in the
fortran code browsing support I wrote
(ELPA:f90-interface-browser).  It also hooks into the etags stack
so that you can pop back, and falls back to etags themselves if
no generic interfaces are found.

Interfacing with the etags stack would have been easier with
callbacks I think, but as with Helmut, I don't like etags'
interface for jumping through multiple definitions and prefer a
method which allows the user to see and pick which definition
they want.

Lawrence

-- 
Lawrence Mitchell <wence@gmx.li>




  parent reply	other threads:[~2013-02-20  9: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
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 [this message]
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=87vc9n8fx5.fsf@gmx.li \
    --to=wence@gmx.li \
    --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).