[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: Fri, 2 Apr 2004 09:16:34 -0500

    juri> I think `*Note' quoted with a preceding
    ` or " character should not be considered as a valid reference

I guess I can't think of a reason to write something like address@hidden' or
"@ref{foo}", and I don't see any cases in reality, so this might be ok,
but neither am I clear as to why it is necessary.  What does
fontification have to do with quote chars?  (Sorry, I could not quickly
make sense of the code.)  Could you explain a little?

    juri> I am not aware of any Info files with references without
    whitespace after `*Note'.  Perhaps somewhere such files may exist
    that was generated by a program other than makeinfo, or was

I agree, the space is always there.  I very much doubt there are
handwritten Info files, or ones generated by something other than
makeinfo/texinfmt.el, that do something different.  I think it is a safe
change.  But keep reading.

    eliz> How about if we instead detect the "*Note:*" case and don't
    treat it as a reference?  

I believe this amounts to *Note:[^*] (vs. *Note:\s).  I think either one
is ok, it won't make any difference in practice.  I slightly tend toward
the latter, because it is clearer to understand "*Note: is always
followed by whitespace" rather than "*Note: is followed by anything
except a *" (which, in practice, is always whitespace).

However, if you really think it is an issue, we can go with the former.

    eliz> (Also the "_Note:_" case, I think.)

I don't think that one is problematic.  No *.


reply via email to

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