From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: using fume with gnu emacs 21.2.1
Date: Fri, 07 Mar 2003 16:40:56 +0100 [thread overview]
Message-ID: <847kbb422f.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: z2u9a.13884$EN3.111842@newsfep4-glfd.server.ntli.net
Chris Jones <c.jones9@ntlworld.com> writes:
> to my .emacs makes imenu start automatically, but is there anything I can
> add to make it up rescan automatically ? I found references to a
> `imenu-auto-rescan' variable but since I know next to nothing about lisp, I
> can't seem to get it to work.....
C-h v imenu-auto-rescan RET gives you the documentation, which tells
you that you can customize the variable. That word is a link,
middle-click on it (or hit RET on it). Then follow the prompts and
don't forget to save your changes.
--
A preposition is not a good thing to end a sentence with.
prev parent reply other threads:[~2003-03-07 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 18:25 using fume with gnu emacs 21.2.1 Chris Jones
2003-03-05 20:27 ` Kai Großjohann
2003-03-05 21:33 ` Chris Jones
2003-03-07 15:40 ` Kai Großjohann [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=847kbb422f.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).