This was considered as well. The problem with this is that you'd like
the Info reader to display `colon' as `:', otherwise it would confuse
users, I think.
It would not confuse them any more than the change you are making in
the source files, which consists of replacing `:' with
On Mon, 18 Mar 2002, Richard Stallman wrote:
This was considered as well. The problem with this is that you'd like
the Info reader to display `colon' as `:', otherwise it would confuse
users, I think.
It would not confuse them any more than the change you are making in
the
BTW, can the Info readers resolve the problem simply by working
backwards to the last : instead of going forwards to the first :?
I feel like I must be missing something obvious or this would have been
done long ago.
For instance, consider this index entry from the autoconf manual, which
is
I see rms's point that changing the sources is bad,
and I see Werner's point that the warning is annoying,
and I see Eli's point that any translation to the word colon will be
confusing for users in one way or another.
So how about if I simply remove the warning about the : in index entries?
This minimal non-macro test worked for me with both texi2dvi -e and
texinfo.tex, which I think is the equivalent of what your macros end
up doing:
\input texinfo
@setfilename macbrace.info
@deffn Escape @t{\@{}
Using @{ with @@deffn.
@end deffn
@bye
You seem to have a different
On Mon, 18 Mar 2002, Karl Berry wrote:
So how about if I simply remove the warning about the : in index entries?
Then we can go back to the status quo.
This is okay with me, assuming that the status quo is good enough to
leave it alone for a while. I thought it wasn't, and that's why the
On Mon, 18 Mar 2002, Karl Berry wrote:
For instance, consider this index entry from the autoconf manual, which
is currently misparsed by both Info and Emacs:
* @%:@: Quadrigraphs.
A regular expression such as (egrep syntax for simplicity):
^\* (.*)(
You can already disable generation of an index by removing the
@printindex xx directive (or commenting it out, or putting it
inside @ignore). What you want is not to disable the index
generation, but to bypass the normal processing of the indexing
command, which is something different.
So let's remove the warning, change the Texinfo sources back to
using : as they should, and give ourselves some time to work on the
real solution.
Excellent idea. I'm now aware of the problem and I can fix my index
entries.
Werner
___
The AIX compiler dies if a trailing ',' exists in a struct definition.
--
albert chin ([EMAIL PROTECTED])
-- snip snip
--- info/infokey.c.orig Mon Mar 18 08:26:04 2002
+++ info/infokey.c Mon Mar 18 08:26:23 2002
@@ -60,7 +60,7 @@
{
info = 0,
ea = 1,
-var = 2,
+var = 2
On Mon, 18 Mar 2002, Werner LEMBERG wrote:
You can already disable generation of an index by removing the
@printindex xx directive (or commenting it out, or putting it
inside @ignore). What you want is not to disable the index
generation, but to bypass the normal processing of the
On Mon, 18 Mar 2002, Karl Berry wrote:
(b) You could have more than one colon in a row (happens a lot in C++,
for example).
Sorry, I don't see the problem.
* foo::bar: nodename.
will still get parsed correctly, seems to me. The .* will swallow
everything up to the
Can someone please tell me why we have the final `:'?
Just came out that way. I agree it's not ideal. I'll see what I can do.
Additionally, the `--no-headers' is far too radical IMHO for HTML
output; it also disables the very nice menu entries. Is there a
possibility to
Date: Mon, 18 Mar 2002 12:11:08 -0500
From: [EMAIL PROTECTED] (Karl Berry)
Two colons in a row signal the end of the menu item and the beginning of
text that the reader ignores. If you can have two colons as part of the
entry itself, how do you tell which one is the ``real''
From: [EMAIL PROTECTED] (Karl Berry)
Date: Mon, 18 Mar 2002 12:16:22 -0500
Can someone please tell me why we have the final `:'?
Just came out that way.
The code seems to do this on purpose:
if (looking_at (::))
discard_until (:);
else
{ /* discard the
On Mon, Mar 18, 2002 at 02:15:12PM -0500, Karl Berry wrote:
The AIX compiler dies if a trailing ',' exists in a struct definition.
Well, sigh.
What version is this? Does this compiler claim to be ANSI compliant?
(I'm wondering if running ansi2knr would help.)
xlc v5.0.2.0, AIX
I don't remember why is it done so, but I'd suggest to be
extra-careful with changing that, especially in a bug-fix release.
I guess if there is a description, then the : makes sense.
Some Name: Some description.
If there is no description, then it's superfluous.
As you suggest, don't
the problem is apparently specific to the handling of @deffn in
makeinfo
Right you are. I must have failed to see the error when I ran
texi2dvi -e. Here's a patch.
It works fine, thanks.
Werner
___
Bug-texinfo mailing list
[EMAIL
Not a real `problem'. But it litters the environment with unused
files (i.e. if there is no @printindex command), and I don't like this
very much. Maybe this is me only.
Oh, I agree the extra empty files are annoying, but it is hard to fix.
There was a patch for this sent years
19 matches
Mail list logo
