From: Gavin Smith <gavinsmith0123@gmail.com>
To: Glenn Morris <rgm@gnu.org>, bug-texinfo@gnu.org, 34023@debbugs.gnu.org
Subject: bug#34023: Support double colons in Info index entries
Date: Fri, 11 Jan 2019 20:14:44 +0000 [thread overview]
Message-ID: <20190111201444.GD14925__39502.8686769821$1547237572$gmane$org@darkstar> (raw)
In-Reply-To: <20190111201323.GC14925@darkstar>
On Fri, Jan 11, 2019 at 08:13:23PM +0000, Gavin Smith wrote:
> On Thu, Jan 10, 2019 at 07:53:52PM -0500, Glenn Morris wrote:
> > Gavin Smith wrote:
> >
> > > This is what is implemented in the standalone info browser (since
> > > change on 2017-04-08).
> >
> > "Defining the Entries of an Index" in the Texinfo manual continues to
> > say (through Texinfo 6.5.90) "Caution: Do not use a colon in an index entry".
>
> Even if Info mode and the standalone Info browser are changed to
> support colons in index entries, people running older versions of these
> won't be able to read them. However, texi2any does output the colon in
> the index entry without complaint. See attached Texinfo input and Info
> output. Newer versions of 'info' can deal with the colons in the index
> entries that are output here.
>
There should still be a warning about this in the Texinfo manual, but it
could be toned down.
next prev parent reply other threads:[~2019-01-11 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 21:14 Support double colons in Info index entries Gavin Smith
2019-01-11 0:04 ` bug#34023: " Juri Linkov
2019-01-11 0:28 ` Drew Adams
2019-01-11 19:46 ` Gavin Smith
[not found] ` <20190111194631.GA14925@darkstar>
2019-01-11 19:49 ` Gavin Smith
2019-01-13 0:55 ` Juri Linkov
2019-01-11 0:53 ` Glenn Morris
2019-01-11 20:13 ` Gavin Smith
2019-01-11 20:14 ` Gavin Smith [this message]
2019-01-11 20:32 ` Glenn Morris
[not found] ` <hek1jbkk9o.fsf@fencepost.gnu.org>
2019-01-16 19:17 ` Gavin Smith
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20190111201444.GD14925__39502.8686769821$1547237572$gmane$org@darkstar' \
--to=gavinsmith0123@gmail.com \
--cc=34023@debbugs.gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.