the @samp{'} character (single quote) in the character
constant, @dfn{escape} it with a backslash (@samp{\}). This character
constant looks like @code{'\''}. The backslash character here
Is there a newer Texinfo release which fixes this?
--
Dr Richard Stallman (https://stallman.org)
Chief
macros are predefined on each kind of machine
(@pxref{System specific Predefined Macros, System specific Predefined
Macros, System-specific Predefined Macros, cpp, The C Preprocessor}). This
allows you to provide code specially tuned for a
particular machine.
--
Dr Richard Stallman (https
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Thanks.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU
orrect: the reference should point to the (cpp) manual instead of the
> (gcc) manual.
What is the full, formal tit;e of the CPP manual? Texinfo cross-references
need to specify that, as well as the short name for Info.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GN
ot;System specific".
I will make that change. Thanks.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
where do these strange numbers come from?
https://gcc.gnu.org/onlinedocs/gcc/System_002dspecific-Predefined-Macros.html#System_002dspecific-Predefined-Macros
Could there be a bug in texi2any that handles hyphen wrong?
0x2d is the hex code for hyphen.
What does the source for that GCC manual sa
ble in makeinfo
that needs to be updated?
makeinfo --version gave me
texi2any (GNU texinfo) 6.7
apt-get install texinfo said I have version 6.7.0.dfsg.2-5
which is the latest version in Trisquel 10.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.
^
> > There should be a comma there, or makeinfo will produce a warning.
>
> I don't see any warning, and I think adding a comma there wouldn't be correct.
You don't see a warning because latest versions of Texinfo stopped
emitting them.
Thanks for the oth
be slanted too in cases like @kbd{a @key{TAB}}, meaning
> press "a" and then press TAB. Otherwise, you might think that you just
> have to press "a".
I see what you mean, but I don't think it will be unclear. I think
people will understand that @key belongs with adjacen
are keys.
However, since we are also using "key" in its vernacular meaning,
in the first line, the result is an inconsistent usage of "key".
That is what creates a confusion here.
Any ideas for how to make this clearer?
--
Dr Richard Stallman
President, Free Software Foundat
w places where @key could
have been taken to refer to something other than user input. They
will be fixed.
So I think it is best for @key never to be slanted.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethallo
quot; and "M-TAB" indicate, that input via keyboard is meant.
The question at hand is, in which circumstances should @key be
slanted, and in which circumstances should it be non-slanted.
What answer do you propose for that?
--
Dr Richard Stallman
President, Free Software Foundati
uld be non-slanted.
> It is @kbd{}, which produces a slanted "M-TAB". And this looks ugly
> IMHO, combined with the non-slanted "TAB".
Is there a better alternative?
What other output would you propose for @kbd{M-@key{TAB}}?
--
Dr Richard Stallman
President, Free
For now, let's
not worry about it.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
x
of an entry in a keymap is always a kind of event. In this case,
it is ESC, which is a keyboard key. So why would @key
not be correct?
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way!
haracter
It is both, isn't it? It is a key to be typed, and we
call it the escape character.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
-@key{TAB}}.
would be non-slanted.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
ou can do other
things with it, such as gaze at it lovingly, caress it, kiss it, or
clean it, but there is no point mentioning those uses in a manual.
Thus, in effect any reference to a key in a manual is about
entering the key as input.
--
Dr Richard Stallman
President, Free Software Foundation (
ext
> that a user types from text that the user doesn't type, but is instead
> the label of a key.
I'm leaning towards agreeing, but I'd like to see
if anyone has an argument for the other choice.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Inte
the slanted font, I think we created this confusion.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
like colored hyperlinks, that is up to you, of course. But, as
demonstrated, it may take a long time for readers who dislike mousing
(like me) to find them :)
Anyway, I hope that my proofreading contributed something and did not
cost too much of your time.
Kind regards & a good weekend,
Er
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Please insert @hyphenation{auto-ma-ti-cal-ly}
in texinfo.tex.
--
Dr Richard
ts own, but I tried copying a separate PDF manual into the same
> directory as a PDF manual with a link to it, and clicking on the link
> worked in that case: it loaded the other manual at the specified
> section.
That being so, there is no bug.
Thanks.
--
Dr Richard Stallman
.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
Texinfo
turns out to be a non-bug. Clicking on them really works
when the other manual is present.
Sorry for the false alarm.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See
of the book into italics (when there is a book name)?
Please ack.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
o The Emacs Lisp Reference Manual.
[2:text/html Show Save:noname (8kB)]
--- End of forwarded message ---
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
f license, then it is free too. But
this condition is a pain in the neck, so the license ought to be
changed.
Who developed TexiWeb Jr? I never heard of it before.
Can you show me its license?
What is jrweave? What does it do? What is its source license?
--
Dr Richard Stallman
President, Free
Please DTRT.
--- Start of forwarded message ---
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS,
UNPARSEABLE_RELAY autolearn=failed version=3.1.0
To: [EMAIL PROTECTED]
From: Katsumi Yamaoka [EMAIL PROTECTED]
Date: Wed, 10 Oct 2007 11:17:10 +0900
I believe that the bug was a badly initialized while loop in
`Info-extract-menu-node-name'.
I would like to commit the following patch, which takes care of these
problems. Is this OK?
If nobody reports problems with it in 2 days, please install it.
(texinfo.tex - texinfo/texinfo.tex) I put in there, so I put it back.
(If you want me to remove it, though, I will.) I'm not sure what we
gain by breaking it.
I have no opinion--thanks for DTRT.
___
Bug-texinfo mailing list
[EMAIL
Here are some minor errors to fix:
man/texinfo.tex:
ftp://ftp.gnu.org/gnu/texinfo.tex - ftp://ftp.gnu.org/gnu/texinfo/texinfo.tex
ftp://ftp.gnu.org/pub/gnu/TeX.README - ftp://ftp.gnu.org/non-gnu/TeX.README
___
Bug-texinfo mailing list
--- Start of forwarded message ---
From: TAKAHASHI Kaoru [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: texinfmt.el: @verb support request
Sender: [EMAIL PROTECTED]
Date: Tue, 03 Dec 2002 21:46:03 +0900
- --Multipart_Tue_Dec__3_21:46:03_2002-1
Content-Type:
And I didn't
change the tramp manual, since it already uses @copying in an unusual
way, and fixing that would have required more changes than I felt
comfortable making.
What precisely is unusual? Could you tell
[EMAIL PROTECTED] about the problem so he can fix it?
rms, eli -- do you think we should change info.texi (and/or the other
emacs manuals) to use the new @copying command? Or do you want to keep
those .texi files processable by older makeinfo's?
Please do change them--the Emacs HEAD sources already depend
on @copying for one manual.
--- Start of forwarded message ---
Sender: [EMAIL PROTECTED]
Date: Thu, 21 Mar 2002 08:16:34 +0100
From: Gunnar Strand [EMAIL PROTECTED]
Organization: Ericsson Erisoft AB
X-Accept-Language: Swedish, sv, en
To: [EMAIL PROTECTED]
Subject: Texinfo source tar missing source?
Hi,
Page:
Let's quickly change Makeinfo to convert colon to `colon'
As I said yesterday: Let's get rid of the warning instead. The index
entries won't work, but that is obviously not a big deal since I
don't remember more than one or two bug reports about it in 10+ years.
Then we
Let's assume that we have a manual
about C++ classes, which describes a class `foo'. Then it will probably
document methods like `foo:foo', `foo:~foo', and `foo:bar'. As a user
who reads that manual and looks for the methods from that class, I'd try
typing i foo: TAB.
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
There has been a proposal to (automatically) use colon instead of :.
This cure seems worse than the disease to me.
It is not perfect, but it seems much better than what we are doing
now, which is changing the @cindex command args to say colon. It is
very easy and the output will work
Can you fix Texinfo to support them?
Yes, we really want to do this. And also eliminate the restrictions on
node names, which is pretty much the same issue. This means a notable
change to Info format
Why so? If you want to really support colon in a menu item name, I
agree
Since running the conversion programs by hand (more likely via make)
does not seem like a big deal to me, I (obviously) have not made it a
high priority.
This seems to affect users' perception of how easy it is to use
Texinfo, so could you try to do this for the next release?
TeX reads the file `filename.eps' (Encapsulated PostScript format).
PDFTeX reads `filename.pdf' (Adobe's Portable Document Format).
makeinfo uses `filename.txt' verbatim for Info output (more or less
as if it was an @example).
makeinfo producing HTML
The feature seems useful. If someone would like to implement it,
I'd be glad to install it.
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
Imagine that the user is reading some large texinfo document (like GNU
Emacs Manual) and wants to make small notes here or there. These notes can
be of two types: user notes (user would like to test that to the details
later, have no time now, have some problem with features
It occurs to me that Texinfo is likely to be responsible
for this problem.
--- Start of forwarded message ---
Date: Tue, 13 Jun 2000 16:09:47 -0700 (PDT)
X-Authentication-Warning: qa-dhcp104.pcx.ncd.com: warrend set sender to
[EMAIL PROTECTED] using -f
From: Warren Dodge [EMAIL
46 matches
Mail list logo
