Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Jarl Friis <jarl@diku.dk>
Subject: Re: get mail from ssh
Date: 25 Sep 2002 11:00:13 +0200	[thread overview]
Message-ID: <m33cry1m1u.fsf@zeus.intra.softace.dk> (raw)
In-Reply-To: <m3admaujb0.fsf@zeus.intra.softace.dk>

Jarl Friis <jarl@diku.dk> writes:

> grossjoh@ls6.informatik.uni-dortmund.de (Kai =?iso-8859-15?q?Gro=DFjohann?=) writes:
> 
> > Clemens Fischer <ino@despammed.com> writes:
> > 
> > > makeinfo --footnote-style=end --no-split tramp.texi
> > > texi2dvi tramp.texi
> > > tex: not found
> > > stdin:119: warning: @menu seen before first @node, creating `Top'
> > > node.
> > > stdin:119: warning: perhaps your @top node should be wrapped in
> > > @ifnottex rather than @ifinfo?.
> > > stdin:119: Next field of node `Top' not pointed to.
> > > stdin:593: This node (Connection types) has the bad Prev.
> > > tex: not found
> > > /usr/local/bin/texi2dvi: tex exited with bad status, quitting.
> > > /usr/local/bin/texi2dvi: see tramp.log for errors.
> > 
> > Whee.  I didn't see these errors.  Btw, the "tex: not found" part is
> > for generating the printable version.  What happens when you manually
> > do
> > 
> >     makeinfo --footnote-style=end --no-split tramp.texi
> 
> "tex: not found" part is *NOT* only for generating the printable
> version.
> 
> 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. makeinfo uses TeX for precessing the texinfo-macros and
> processing the texinfo docuemnt.
> 
> So, yes you do need TeX even just to get the info files!

It certainly seems that I am not correct on this, sorry on the
mis-info.

Jarl


      parent reply	other threads:[~2002-09-25  9:00 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
2002-09-25  9:00                 ` Jarl Friis [this message]

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=m33cry1m1u.fsf@zeus.intra.softace.dk \
    --to=jarl@diku.dk \
    /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).