From: Juanma Barranquero <lekktu@gmail.com>
To: eric@siege-engine.com
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Identifying DEFUNs in which-func-mode
Date: Wed, 7 Oct 2009 04:44:52 +0200 [thread overview]
Message-ID: <f7ccd24b0910061944t540352ben4381b0426395b0a4@mail.gmail.com> (raw)
In-Reply-To: <1254882587.6961.281.camel@projectile.siege-engine.com>
On Wed, Oct 7, 2009 at 04:29, Eric M. Ludlam <eric@siege-engine.com> wrote:
> If you enable semantic-mode in Emacs (via the recent integration) and
> also enable EDE (via the integration), then Emacs will identify your
> Emacs sources as a project, and setup the parsing system to recognize
> DEFUN macros.
Interesting.
> Anyway, the Semantic parsers put overlays on tags, so looking up which
> function you are on is very fast.
Cool. There's a comment in which-func.el:
;; TODO LIST
;; ---------
;; [...]
;; 2. This package should be realized with the help of overlay
;; properties instead of imenu--index-alist variable.
so it's nice to know Semantic is doing better and faster (not that I
doubted it :-)
> You can see how the which-func support works at the bottom of this file:
>
> http://cedet.cvs.sourceforge.net/viewvc/*checkout*/cedet/cedet/semantic/semantic-imenu.el
>
> This support was added a long time ago, and judging by the description
> you posted, should be re-written to some new APIs anyway. I'd be glad
> to see that old code refreshed as needed, as which-func is exactly the
> type of functionality that CEDET excels at.
I've just taken a cursory glance, but yes, it seems like the advice
stuff for which-func at the end of semantic-imenu.el could be
simplified by using which-func-functions.
BTW, there's no semantic/imenu.el on the Emacs CVS, nor any reference
to which-func in the lisp/cedet/ subtree. Why?
> On the flip-side, if you enable the CEDET tools, you could enable
> semantic-stickyfunc-mode instead of which-func. IMO this is a much
> slicker way of doing the same thing, but only if you don't use your
> header line for other tasks already.
It's pretty clear that at some not-to-distant future I should take the
time to learn about the CEDET tools...
All in all, what I proposed could still be useful for developers not
wanting to use EDE, etc. But perhaps is just not worth the trouble.
Juanma
next prev parent reply other threads:[~2009-10-07 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 1:27 Identifying DEFUNs in which-func-mode Juanma Barranquero
2009-10-07 2:29 ` Eric M. Ludlam
2009-10-07 2:44 ` Juanma Barranquero [this message]
2009-10-07 5:38 ` Chong Yidong
2009-10-07 16:23 ` Eric M. Ludlam
2009-10-07 16:28 ` Juanma Barranquero
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=f7ccd24b0910061944t540352ben4381b0426395b0a4@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
/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).