From: Jesper Harder <harder@myrealbox.com>
Subject: Re: get mail from ssh
Date: Sun, 22 Sep 2002 19:43:21 +0200 [thread overview]
Message-ID: <m3ofapor7q.fsf@defun.localdomain> (raw)
In-Reply-To: <m3admaujb0.fsf@zeus.intra.softace.dk>
Jarl Friis <jarl@diku.dk> writes:
> texinfo certanly requires TeX. texinfo files are a TeX-files! (they
> are just not plain-tex files)
>
> The first line in a texinfo file contains "\input texinfo" which loads
> the texinfo format all the macros that makes up the texinfo-tags.
Yes, but that's only used when you process the file with TeX.
> makeinfo uses TeX for precessing the texinfo-macros and processing the
> texinfo docuemnt.
Nope, 'makeinfo' doesn't use TeX. Of course, 'texi2dvi' and 'texi2pdf'
*do* need TeX -- but you don't need it if you only want info files.
> So, yes you do need TeX even just to get the info files!
Try removing or renaming your tex executable, and try this:
$ tex
bash: tex: command not found
$ makeinfo message.texi
$ ls message*
message message-1 message-2 message.texi
next prev parent reply other threads:[~2002-09-22 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8c53236b.0209141953.7df583fc@posting.google.com>
2002-09-16 3:10 ` Wu XiaoGuang
2002-09-16 10:18 ` Kai Großjohann
2002-09-17 3:20 ` Wu XiaoGuang
[not found] ` <8765x7qat7.fsf@labatt.uhoreg.ca>
2002-09-17 13:37 ` Kai Großjohann
[not found] ` <7khlopj2.fsf@ID-23066.news.dfncis.de>
[not found] ` <vafu1korb16.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <d6r832ro.fsf@ID-23066.news.dfncis.de>
[not found] ` <m3sn042tyf.fsf@multivac.cwru.edu>
2002-09-21 16:11 ` Clemens Fischer
[not found] ` <vafu1kifmag.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <m3admaujb0.fsf@zeus.intra.softace.dk>
2002-09-22 17:01 ` Kai Großjohann
2002-09-22 17:24 ` Russ Allbery
2002-09-22 17:43 ` Jesper Harder [this message]
2002-09-25 9:00 ` Jarl Friis
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=m3ofapor7q.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).