Re: bug#34023: Support double colons in Info index entries

2019-01-11 Thread Glenn Morris
Gavin Smith wrote: > 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. Sure. However, if Texinfo is intending to support them from version X, IMO it should document that. > Ho

Re: bug#34023: Support double colons in Info index entries

2019-01-10 Thread Glenn Morris
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".

Re: bug#13965: info.info conflict between emacs and texinfo

2015-10-18 Thread Glenn Morris
PPS Personally speaking, if I were packaging Emacs for a distribution, I'd remove info.info from the installed files, and (probably) make the Emacs package depend on the (in comparison tiny) Info package that provides it. (It seems to be basically an essential package anyway, on Red Hat at least).

Re: bug#13965: info.info conflict between emacs and texinfo

2015-10-18 Thread Glenn Morris
Andreas Schwab wrote: > Two packages fighting for the same file is bad. Someone once told me that these things happen, and should be solved in the packages, not the source. http://lists.gnu.org/archive/html/emacs-devel/2014-03/msg01211.html

Re: bug#13965: info.info conflict between emacs and texinfo

2015-10-18 Thread Glenn Morris
Glenn Morris wrote: > ii) was solved two-years ago on RedHat-based systems in the rpm > https://bugzilla.redhat.com/show_bug.cgi?id=927996#c11 PS I don't think that's a great solution, but I guess it's good enough. So if there's any interest in Texinfo retaining

Re: bug#13965: info.info conflict between emacs and texinfo

2015-10-18 Thread Glenn Morris
Gavin Smith wrote: >> I'm sure there are many systems where Texinfo is installed and Emacs is not. >> How are people on those systems supposed to learn how to use the >> stand-alone info reader? > > It has its own manual. It doesn't have a tutorial, though. This would > have to be added. It should

Re: bug#13965: info.info conflict between emacs and texinfo

2015-10-17 Thread Glenn Morris
Gavin Smith wrote: > I've removed it from Texinfo, for now. Unless it's changed back, the > file will not be present in the next Texinfo release. I'm sure there are many systems where Texinfo is installed and Emacs is not. How are people on those systems supposed to learn how to use the stand-alo

Using --program-suffix argument to configure gives broken makeinfo link

2014-05-02 Thread Glenn Morris
I configured texinfo-5.2 like this: ./configure --program-suffix"-5" make install created a broken link in bin/: makeinfo -> texi2any This should be: makeinfo-5 > texi2any-5

Re: Warn about invalid index entries

2014-02-05 Thread Glenn Morris
PS Maybe consider adding a --strict flag or somesuch, which will warn about "things that are invalid but which are normally silently accepted for historical reasons"...

Warn about invalid index entries

2014-02-05 Thread Glenn Morris
Hi, The Texinfo manual says: Caution: Do not use a colon in an index entry. In Info, a colon separates the menu entry name from the node name, so a colon in the entry itself confuses Info. Yet makeinfo happily accepts such index entries with no complaint. (For example, I have jus

Re: Warn about invalid node names

2013-08-12 Thread Glenn Morris
Per Bothner wrote (on Mon, 12 Aug 2013 at 09:33 -0700): > In both cases, Werner is not opposed to warnings - he explicitly > says he doesn't want to use --no-warn because he wants useful warnings. > > The problem is warnings that one can't shut up - he is asking for > how to rewrite to source to

Re: Warn about invalid node names

2013-08-12 Thread Glenn Morris
Karl Berry wrote (on Wed, 7 Aug 2013 at 23:12 GMT): > Surely these people can live with the warnings, or use --no-warn? > > No, people absolutely hate warnings, and absolutely hate using --no-warn. Really? This position makes no sense to me. Why wouldn't you want to be warned about somethin

Warn about invalid node names

2013-08-07 Thread Glenn Morris
Hi, The Texinfo manual says: Unfortunately, you cannot use periods, commas, colons or parentheses within a node name Yet makeinfo happily accepts such node names with no complaint. I really can't see why you would not warn about such things by default. I'm not the first to say this: htt

Re: bug#13965: info.info conflict between emacs and texinfo

2013-04-02 Thread Glenn Morris
Karl Berry wrote: > The point is that nearly every other package in GNU uses fdl.texi (as > far as I have seen). Why should Emacs use a different name for the > file? No reason other than history/inertia AFAIK. It's always been "doclicense.texi", for ~ 13 years now.

Re: bug#13965: info.info conflict between emacs and texinfo

2013-04-02 Thread Glenn Morris
Karl Berry wrote: > +@include doclicense.texi > > How about naming the file fdl.texi, like virtually every other package does? If it really helps you, we could rename it. We'll have to change 58 files, several of which also live in other repositories. It won't make any difference to this is

Re: bug#13965: info.info conflict between emacs and texinfo

2013-03-29 Thread Glenn Morris
PS AFAIK, the only reason it is in Emacs is because of MS Windows users. I doubt anyone on POSIX platforms uses info pages without having texinfo installed.

Re: bug#13965: info.info conflict between emacs and texinfo

2013-03-29 Thread Glenn Morris
Karl Berry wrote: > Both emacs and texinfo install the info.info info file. This needs to > be resolved. Why does it matter? It is the same file, just provided by two packages. > Fine, I'll remove it from Texinfo, since in practice info.texi has been > maintained in Emacs for many years

Double hyphens in variable names

2012-11-02 Thread Glenn Morris
Hi, I wrote this in a .texi file: @defvar cl--gensym-counter This variable holds the counter used to generate... @end defvar I noticed that in the info file generated by makeinfo (4.13), this appears as: -- Variable: cl-gensym-counter This variable holds the counter used to generate..