unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org
Subject: Re: Problem building emacs-lisp-intro.dvi.
Date: Mon, 21 Aug 2006 23:26:03 +0200	[thread overview]
Message-ID: <87ac5xvl04.fsf@xs4all.nl> (raw)
In-Reply-To: <m1GFFB9-0004OkC@rattlesnake.com> (Robert J. Chassell's message of "Mon, 21 Aug 2006 19:11:19 +0000 (UTC)")

"Robert J. Chassell" <bob@rattlesnake.com> writes:

> That is an excellent idea!  I have deleted lispintro/texinfo.tex,
> changed lispintro/emacs-lisp-intro.texi appropriately, and tested it
> with `make emacs-lisp-intro.dvi' in lispintro/.  No reported errors.
> I have committed the changes.

Instead of hardcoding the use of man/texinfo.tex into
lispintro/emacs-lisp-intro.texi, you could also use the -I switch of
texi2dvi to specify the man directory.  (I recently did this in
lispref/Makefile.in for building lispref/elisp.dvi.)  That way nothing
special needs to be done when the manual is built on its own.

  Lute.

  reply	other threads:[~2006-08-21 21:26 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 [this message]
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
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=87ac5xvl04.fsf@xs4all.nl \
    --to=lute.kamstra.lists@xs4all.nl \
    --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).