[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] ignoring Info extensions

From: Karl Berry
Subject: Re: [PATCH] ignoring Info extensions
Date: Thu, 1 Apr 2004 20:50:01 -0500

    Perhaps makeinfo should produce a warning about it, but still

It does now (in the current sources, in some circumstances).

    [ \t\n]+\*[Nn]ote[ \t\n]+

There are many cases where the preceding character is not whitespace,
such as (@pxref{foo}) -> (*note foo::).  So that part of the proposed
regexp won't work.

However, I cannot find or think of any case where the *following*
character will not be whitespace.  Looking at makeinfo/xref.c and
texinfmt.el, it looks to me like when *[nN]ote is output, it is always
followed by a space.  So it seems this would be a good improvement!

I don't think anything else generates Info files, and even if it does,
it seems highly unlikely it would output anything else.

Eli, can you think of a way
  \*[Nn]ote[ \t\n]+
could fail?  I also looked in all the dozens of info files installed on
my system, and could not find any problematic cases.

As Juri says, there are tons of places where "*Note*" is output for
various reasons.  It would be nice if it just worked, this has been a
longstanding nagging problem.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]