unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Indices in Info.
Date: Tue, 24 Jun 2003 07:17:35 +0300	[thread overview]
Message-ID: <9743-Tue24Jun2003071734+0300-eliz@elta.co.il> (raw)
In-Reply-To: <200306240342.h5O3guf14997@eel.dms.auburn.edu> (message from Luc Teirlinck on Mon, 23 Jun 2003 22:42:56 -0500 (CDT))

> Date: Mon, 23 Jun 2003 22:42:56 -0500 (CDT)
> From: Luc Teirlinck <teirllm@dms.auburn.edu>
> 
> g (texinfo)Concept Index
> 
> Click on:
> 
> * $Id::                                  GNU Sample Texts.

This menu entry should not be there.  It's a bug in texinfo.txi and/or
makeinfo.

> Proposed solution:  Just institute a convention that an index entry
> should never end in a colon.

The Texinfo manual already disallows such cases.  But there's a need
to support node names with colons (think about a manual about a C++
library, for example), so there are various hacks out there to get
Info readers to have some support for that.

> If it is worth while for Emacs Info to support those computer
> programming language terms, it might also be worth while for the
> stand-alone version to do so.

True; but doing that is not easy.  The stand-alone Info doesn't use
regexps when it searches for specific text patterns such as the one in
a menu, and the same code is used for cross-references and whatsnot.

IMHO, these tricky cases should be solved by a change in the Info file
format, not by hacks specific to this or that reader.

  reply	other threads:[~2003-06-24  4:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24  3:42 Indices in Info Luc Teirlinck
2003-06-24  4:17 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-24 13:26 Karl Berry
2003-06-24 14:04 ` Andreas Schwab
2003-06-25  1:35 ` Luc Teirlinck
2003-06-25  1:55   ` Luc Teirlinck
2003-06-25  3:26     ` Luc Teirlinck
2003-06-25 17:50     ` Stefan Monnier
2003-06-25 19:53   ` Richard Stallman
2003-06-24 14:08 Karl Berry

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=9743-Tue24Jun2003071734+0300-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --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).