From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15996@debbugs.gnu.org
Subject: bug#15996: 24.3.50; imenu inconsistencies
Date: Sun, 01 Dec 2013 09:11:34 +0100 [thread overview]
Message-ID: <87ob51ng7d.fsf@gmail.com> (raw)
In-Reply-To: <jwv7gbre0dr.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Fri, 29 Nov 2013 09:44:33 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> (defvar foo)
> [...]
>> 1) var `foo' is not listed,
>
> That's on purpose. Of course, it's not always the right choice, but
> imenu is supposed to let you go to the "definition" of something and
> this is not a definition.
>
>> 2) The "defun*" in var `baz' is detected as a function with name `.',
>> but is not, it is just an element of var `baz'.
>
> Yes, that's a false positive. It's difficult/impossible to avoid all
> false positives and all false negatives. We could try and recognize
> this particular case with ad-hoc code, but it wouldn't help in general.
>
>> 3) The function test defined with `defun*' from cl package is listed,
>> but the macro `test2' defined with `defmacro*' is not listed.
>> I expect the both listed if cl package is loaded or nothing listed if it
>> is not loaded.
>
> Agreed.
Here another one (Reported on helm issues):
here a file test.c:
--8<---------------cut here---------------start------------->8---
void foo(); // either item in the imenu list jumps here
void foo() {}
--8<---------------cut here---------------end--------------->8---
Imenu show only one "foo".
(semantic-mode 1)
Imenu show now the two "foo".
See:
https://github.com/emacs-helm/helm/issues/337
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
prev parent reply other threads:[~2013-12-01 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 7:44 bug#15996: 24.3.50; imenu inconsistencies Thierry Volpiatto
2013-11-29 14:44 ` Stefan Monnier
2013-12-01 8:11 ` Thierry Volpiatto [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ob51ng7d.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=15996@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.