From: Didier Verna <didier@xemacs.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: Mixing whitespace and topical changes
Date: Tue, 17 Apr 2007 11:39:41 +0200 [thread overview]
Message-ID: <muxabx7z6ea.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <muxfy6zz6qi.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Tue\, 17 Apr 2007 11\:32\:21 +0200")
I wrote:
> OK, for some reason, I missed this message. My apologies.
Actually, the texinfo documentation clearly demonstrates that I have no
excuses:
*Caution:* Do not use tabs in a Texinfo file! TeX uses
variable-width fonts, which means that it cannot predefine a tab
to work in all circumstances. Consequently, TeX treats tabs like
single spaces, and that is not what they look like. Furthermore,
`makeinfo' does nothing special with tabs, and thus a tab character
in your input file may appear differently in the output.
To avoid this problem, Texinfo mode causes GNU Emacs to insert
multiple spaces when you press the <TAB> key.
Also, you can run `untabify' in Emacs to convert tabs in a region
to multiple spaces.
Don't use tabs.
--
Read the Jazz Blog !! http://jazzblog.didierverna.com
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier@xemacs.org
next prev parent reply other threads:[~2007-04-17 9:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 19:05 Reiner Steib
2007-04-16 13:17 ` Didier Verna
2007-04-17 2:04 ` Katsumi Yamaoka
2007-04-17 7:14 ` Didier Verna
2007-04-17 8:05 ` Katsumi Yamaoka
2007-04-17 9:32 ` Didier Verna
2007-04-17 9:39 ` Didier Verna [this message]
2007-04-17 10:21 ` Katsumi Yamaoka
2007-04-17 23:42 ` Miles Bader
2007-04-18 8:50 ` Didier Verna
2007-04-18 9:15 ` Miles Bader
2007-04-17 17:25 ` Reiner Steib
2007-04-18 7:42 ` Didier Verna
2007-04-18 9:54 ` Didier Verna
2007-04-18 20:55 ` Reiner Steib
2007-04-19 7:17 ` Didier Verna
2007-04-19 7:39 ` Miles Bader
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=muxabx7z6ea.fsf@uzeb.lrde.epita.fr \
--to=didier@xemacs.org \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).