unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problem building emacs-lisp-intro.dvi.
Date: Wed, 23 Aug 2006 11:49:27 -0400	[thread overview]
Message-ID: <E1GFuyt-00029T-Qr@fencepost.gnu.org> (raw)
In-Reply-To: <m1GFTSz-0004SKC@rattlesnake.com> (bob@rattlesnake.com)

> Date: Tue, 22 Aug 2006 10:26:41 +0000 (UTC)
> From: "Robert J. Chassell" <bob@rattlesnake.com>
> Cc: emacs-devel@gnu.org
> 
> Eli said
> 
>     IIRC, the -I switch was supported by makeinfo since day one.
> 
> which may be the case.  However, the Texinfo manual (version 4.8, 29
> December 2004) says
> 
> `-I DIR'
>      Append DIR to the directory search list for finding files that are
>      included using the `@include' command.  By default, `makeinfo'
>      searches only the current directory.  If DIR is not given, the
>      current directory `.' is appended.  Note that DIR can actually be
>      a list of several directories separated by the usual path
>      separator character (`:' on Unix, `;' on MS-DOS/MS-Windows).
> 
> I do not know whether texinfo.tex, which is input with a `\input'
> command, is considered an `@include' file.

Sorry, I confused the issue: the -I switch to texi2dvi has nothing at
all to do with makeinfo, since makeinfo doesn't need to read
texinfo.tex.  texinfo.tex is read by TeX; makeinfo simply ignores the
"\input texinfo.tex" line.

So the question here is whether texi2dvi invokes TeX in a way that
would find texinfo.tex in a directory mentione in the -I switch.

  parent reply	other threads:[~2006-08-23 15:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 11:19 Problem building emacs-lisp-intro.dvi Lute Kamstra
2006-08-21 14:50 ` Robert J. Chassell
2006-08-21 15:24   ` Lute Kamstra
2006-08-21 19:11     ` Robert J. Chassell
2006-08-21 21:26       ` Lute Kamstra
2006-08-22  0:45         ` Robert J. Chassell
2006-08-22  1:29           ` Eli Zaretskii
2006-08-22  7:53           ` David Kastrup
2006-08-22 10:26             ` Robert J. Chassell
2006-08-22 10:29               ` David Kastrup
2006-08-22 17:51                 ` Robert J. Chassell
2006-08-23 15:49               ` Eli Zaretskii [this message]
2006-08-23 16:26                 ` Andreas Schwab
2006-08-23 19:11                   ` Robert J. Chassell
2006-08-22 10:30             ` Robert J. Chassell

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1GFuyt-00029T-Qr@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).