From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Cc: epameinondas@gmx.de, emacs-devel@gnu.org
Subject: Re: Double hyphens in variable names.
Date: Fri, 03 Oct 2003 21:37:42 +0200 [thread overview]
Message-ID: <sgd7k3mnmd5.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <200310031618.h93GIpw14398@raven.dms.auburn.edu> (Luc Teirlinck's message of "Fri, 3 Oct 2003 11:18:51 -0500 (CDT)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Lute Kamstra wrote:
>
> Imenu's functionality can be easily explained without referring to
> imenu--info-alist, so I think I'll do that.
>
> I guess you really mean imenu--index-alist.
Yes, me braindead.
> If I understand correctly, (elisp)Imenu explains how a major mode
> author can help construct imenu--index-alist in various ways. The
> major mode author is not supposed to play around with
> imenu--index-alist directly. But is taking a look at
> imenu--index-alist not useful for the author to check his work?
> Also could knowing about the alist he is trying to construct with
> the other functions not be useful in understanding those other
> functions? (Assuming my above interpretation of the facts is
> correct).
The author could just check the return value of the
imenu-create-index-function function that (s)he is writing. Note that
I do describe this return value in detail. I also mention that the
two other ways of setting up Imenu work through
imenu-create-index-function's default function. I think that knowing
the name of the variable in which Imenu stores the return value is
only important when hacking on Imenu itself.
> I saw you removed the documentation for the variable. If you really
> think it ought to be removed, then that is OK.
Yes, I do.
> I am not necessarily contesting that removal. You know the node
> better than I do. I just took a quick look at it. However, as a
> solution to the double dash problem, removal seems a little bit too
> radical.
Getting rid of that problem is a nice by-product. :-)
> I believe the following works in all situations, main text and index
> of both Info and printed output:
>
> @defvar {imenu-@--index-alist}
>
> OK this is ugly, but you could mention in the Texinfo source in a
> comment that the ugliness is a work-around for a bug in Texinfo.
> The @- allows for a discretionary hyphen, but the text is short, so
> no problem. The braces around the entire name prevent the Info
> index from just listing `imenu-'. This will work even if the user
> does not have makeinfo 4.7 or higher. The current problems in Info
> need to be fixed, but any such fix will require the user to install
> make-info version 4.7 or higher.
Indeed, that seems to work well. Thanks for the tip.
> (I believe 4.6 is still the latest released version.)
Yes.
Lute.
next prev parent reply other threads:[~2003-10-03 19:37 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 [this message]
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
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 3:51 ` Luc Teirlinck
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-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=sgd7k3mnmd5.fsf@occarina.pna.cwi.nl \
--to=lute.kamstra@cwi.nl \
--cc=emacs-devel@gnu.org \
--cc=epameinondas@gmx.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.
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).