From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Cc: emacs-devel@gnu.org
Subject: Re: Double hyphens in variable names.
Date: Mon, 06 Oct 2003 09:11:32 +0200 [thread overview]
Message-ID: <sgd8ynyx2l7.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <3F7EA544.8080308@wanadoo.fr> (David Ponce's message of "Sat, 04 Oct 2003 12:47:32 +0200")
David Ponce <david.ponce@wanadoo.fr> writes:
>> When writing a major mode, you should never set imenu--index-alist
>> directly; nor should you have to use its value. So it is not part
>> of Imenu's interface and therefore it is an internal variable.
>
> Perhaps there is a case it is necessary to use `imenu--index-alist':
> to force a rescan of the imenu.
>
> For example, the Semantic toolkit set `imenu--index-alist' to nil to
> force a rebuild of the imenu when the user customized an option that
> change how the imenu will be organized (item sorted and/or grouped
> in a different way).
>
> Is there another "standard" method to force a rescan of the imenu
> without using `imenu--index-alist'?
No, not on the lisp level. There is a user-level way to do this: by
selecting the *Rescan* item from Imenu's menu. Setting
imenu--index-alist to nil might work but it's not documented. As it
seems useful for lisp programs to be able to force a rescan, we could
implement such a feature. I'll try and see if I can come up with a
function that does this.
Lute.
next prev parent reply other threads:[~2003-10-06 7:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 13:53 Double hyphens in variable names Lute Kamstra
2003-10-02 5:55 ` Eli Zaretskii
2003-10-02 8:43 ` Lute Kamstra
2003-10-02 13:18 ` Luc Teirlinck
2003-10-02 15:11 ` Lute Kamstra
2003-10-02 16:00 ` Luc Teirlinck
2003-10-02 16:14 ` Lute Kamstra
2003-10-02 16:54 ` Andreas Schwab
2003-10-02 17:25 ` Luc Teirlinck
2003-10-03 1:50 ` Luc Teirlinck
2003-10-03 2:13 ` Luc Teirlinck
2003-10-03 3:45 ` Luc Teirlinck
2003-10-02 19:04 ` Oliver Scholz
2003-10-03 8:39 ` Lute Kamstra
2003-10-03 16:18 ` Luc Teirlinck
2003-10-03 19:37 ` Lute Kamstra
2003-10-03 18:33 ` Luc Teirlinck
2003-10-03 18:42 ` Luc Teirlinck
2003-10-03 19:46 ` Lute Kamstra
2003-10-04 10:47 ` David Ponce
2003-10-06 7:11 ` Lute Kamstra [this message]
2003-10-06 23:19 ` Juri Linkov
2003-10-07 9:08 ` Lute Kamstra
2003-10-03 19:42 ` Richard Stallman
2003-10-03 21:19 ` Juri Linkov
2003-10-02 14:07 ` Luc Teirlinck
2003-10-02 19:15 ` Richard Stallman
2003-10-02 18:56 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2003-10-04 1:03 Karl Berry
2003-10-04 22:35 ` Richard Stallman
2003-10-05 0:53 ` Miles Bader
2003-10-05 10:36 ` Stepan Kasal
2003-10-05 8:34 ` Werner LEMBERG
2003-10-04 1:03 Karl Berry
2003-10-04 3:51 ` Luc Teirlinck
2003-10-06 9:06 David PONCE
2003-10-06 9:18 ` Lute Kamstra
2003-10-07 5:32 ` Richard Stallman
2003-10-07 6:57 ` Lute Kamstra
2003-10-06 9:26 David PONCE
2003-10-07 7:57 David PONCE
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=sgd8ynyx2l7.fsf@occarina.pna.cwi.nl \
--to=lute.kamstra@cwi.nl \
--cc=emacs-devel@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.
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).