From: Josh <josh@foxtail.org>
To: ams@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: emacs-lisp-mode and find-tag
Date: Fri, 20 Jun 2014 09:52:41 -0700 [thread overview]
Message-ID: <CANdFEAH_XRGGMjp5PE5MQGamXxORVM=OZhtr_A7SideJt2sDhg@mail.gmail.com> (raw)
In-Reply-To: <E1Wy16k-0003HP-AC@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Fri, Jun 20, 2014 at 8:52 AM, Alfred M. Szmidt <ams@gnu.org> wrote:
>
> I think it would be good to provide a generic M-. (and M-*, ..)
> binding that several backends (etags, symbol-file, ...) can then
> use.
>
> That would be very nice indeed.
>
+1. There was a discussion[0] about this topic last year and
apparent agreement in principle, but the details are yet to be
worked out. At least two implementations exist already, one
being the patch Leo submitted with that bug and the other being
the `elisp-slime-nav' package I mentioned in that thread (and
whose author has also assigned copyright).
If we do define a standard set of source navigation key bindings,
I hope it includes one for jumping to symbols' references. Unlike
M-. for jumping to definitions, jumping to references doesn't seem
to have a standard binding, even though it's often very handy.
[0] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15641
Josh
[-- Attachment #2: Type: text/html, Size: 1656 bytes --]
next prev parent reply other threads:[~2014-06-20 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 12:32 emacs-lisp-mode and find-tag Alfred M. Szmidt
2014-06-20 13:08 ` Eli Zaretskii
2014-06-20 15:52 ` Alfred M. Szmidt
2014-06-20 14:30 ` Stefan Monnier
2014-06-20 15:52 ` Alfred M. Szmidt
2014-06-20 16:24 ` Stefan Monnier
2014-06-20 16:52 ` Josh [this message]
2014-06-20 17:35 ` Stefan Monnier
2014-06-20 18:53 ` Ivan Kanis
2014-06-20 19:07 ` Josh
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 20:22 Barry OReilly
2014-06-21 1:08 ` Stefan Monnier
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='CANdFEAH_XRGGMjp5PE5MQGamXxORVM=OZhtr_A7SideJt2sDhg@mail.gmail.com' \
--to=josh@foxtail.org \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).