From: Doug Lewan <dougl@shubertticketing.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: which-func/imenu
Date: Tue, 7 Aug 2012 12:51:15 +0000 [thread overview]
Message-ID: <155DEC68569B714B86C2C7075F5EDA98268CC9A5@DAKIYA1.pegasus.local> (raw)
In-Reply-To: <5020BCA6.6040408@easy-emacs.de>
Thanks. I'll give it a try.
> -----Original Message-----
> From: help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org
> [mailto:help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org] On
> Behalf Of Andreas Röhler
> Sent: Tuesday, 2012 August 07 02:59
> To: help-gnu-emacs@gnu.org
> Subject: Re: which-func/imenu
>
> Am 06.08.2012 21:38, schrieb Doug Lewan:
> > Just what do I have to do to make which-function-mode aware of a new
> language? I haven't been able to entirely disentangle the
> documentation.
> >
> > I think I know the following.
> > * I need imenu.
> > * I have to create imenu-generic-expression. (My world is simple. I
> think the value (nil "procedure\\s-+\\(?1:[[:alnum:]]+\\)" 2) should
> do. But I have been wrong one other time.)
> > * I need to add the mode (as a symbol) to which-func-modes.
>
> imenu--index-alist is in the center of things here.
> If it gets filled, which-func-modes should work right out of the box.
>
>
> >
> > This is, however, not enough to "support Imenu", in the words of
> emacs Info section 26.2.4.
> > What should I really be doing?
> >
> > ,Douglas
> > Douglas Lewan
> > Shubert Ticketing
> > (201) 489-8600 ext 224
> > Optimism is an occupational hazard of programming: testing is the
> treatment. - - K. Beck
> >
> >
> >
>
prev parent reply other threads:[~2012-08-07 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 19:38 which-func/imenu Doug Lewan
2012-08-07 6:58 ` which-func/imenu Andreas Röhler
2012-08-07 12:51 ` Doug Lewan [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
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=155DEC68569B714B86C2C7075F5EDA98268CC9A5@DAKIYA1.pegasus.local \
--to=dougl@shubertticketing.com \
--cc=andreas.roehler@easy-emacs.de \
--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).