From: Drew Adams <drew.adams@oracle.com>
To: William Xu <william.xwl@gmail.com>
Cc: 15560@debbugs.gnu.org
Subject: bug#15560: 24.3.50; [patch] * imenu.el (imenu--generic-function): Don't generate index for comments area.
Date: Wed, 9 Oct 2013 07:31:11 -0700 (PDT) [thread overview]
Message-ID: <e8851775-5b45-4aff-b509-2c3a31b33b2b@default> (raw)
In-Reply-To: <CACzMC-CNENoqY54DSSxFj8kWKqvJt3cpG0+q7=Sq2V28+BenQA@mail.gmail.com>
> > It is annoying when imenu generates index also for functions found
> > in comments area.
>
> Yes! And no. It depends what you want at the particular time.
> ^^^^
> Sometimes you have multiple versions of a definition, with all
> but one commented out, and you *want* Imenu to present you with
> all of them, for easy navigation among them.
>
> In the source codes i'm working with, there are very long change history at the
> beginning of file. So for me, imenu becomes almost useless. I'm using imenu as
> a function indexer, like those in modern IDEs, where they usually ignore
> commentted defs.-William
Did you see my emphatic "Yes!"?
I agree that this is usually the behavior one wants, which is why I
implemented it (years ago), and why I chose ignoring commented definitions
as the default behavior.
My point is that sometimes it can be useful to not ignore commented
definitions, and that users should be the ones to choose the behavior that
is most useful to them. That's all.
next prev parent reply other threads:[~2013-10-09 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 8:17 bug#15560: 24.3.50; [patch] * imenu.el (imenu--generic-function): Don't generate index for comments area William Xu
2013-10-08 21:58 ` Drew Adams
2013-10-09 9:21 ` William Xu
2013-10-09 12:23 ` Stefan Monnier
2013-10-09 14:31 ` Drew Adams
2013-10-09 14:31 ` Drew Adams [this message]
2013-11-24 21:28 ` Dmitry Gutov
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=e8851775-5b45-4aff-b509-2c3a31b33b2b@default \
--to=drew.adams@oracle.com \
--cc=15560@debbugs.gnu.org \
--cc=william.xwl@gmail.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 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.