From: Nathaniel Flath <flat0103@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Semantic and Imenu
Date: Mon, 26 Apr 2010 19:14:18 -0700 [thread overview]
Message-ID: <s2z5e3a506e1004261914r9c34ddakce5881eb0765ef34@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
Hello,
I'm using JDEE for Java development, which requires me to have CEDET.
However, Cedet seems to be breaking imenu; in many modes(including
emacs-lisp-mode) it sets imenu-create-index-function to
semantic-create-imenu-index, which causes Imenu to thinkj there are no items
suitable for an index in the current buffer. Is there a way to either
prevent CEDET from hijacking Imenu or have it actually analyze the buffer
correctly? I only do
(require 'cedet)
(require 'jde)
As things that would influence CEDET.
Thanks,
Nathaniel Flath
[-- Attachment #2: Type: text/html, Size: 588 bytes --]
next reply other threads:[~2010-04-27 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 2:14 Nathaniel Flath [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 13:28 Semantic and imenu Kai Großjohann
2002-09-14 8:23 ` maierh
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=s2z5e3a506e1004261914r9c34ddakce5881eb0765ef34@mail.gmail.com \
--to=flat0103@gmail.com \
--cc=help-gnu-emacs@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.
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).