From: ecashin@coe.uga.edu (Ed L. Cashin)
Cc: ntg-context@ntg.nl, Thomas Esser <te@informatik.uni-hannover.de>
Subject: Re: RH 6.0 teTeX (was Re: seeking ConTeXt code) (long)
Date: 07 Sep 1999 10:45:59 -0400 [thread overview]
Message-ID: <vhoso4q2314.fsf@jane.coe.uga.edu> (raw)
In-Reply-To: Hans Hagen's message of "Tue, 07 Sep 1999 09:54:01 +0200"
Hans Hagen <pragma@wxs.nl> writes:
> "Ed L. Cashin" wrote:
[ having trouble with "Hello, World!" in ConTeXt ]
> >
> > line 171: inserting E-TEX code etex.src etexdefs.lib
> > ! I can't find file `etex.src'.
> > l.183 \normalinput etex.src
...
> Can you check the texmf.cnf file and see if the etex path is added to
> the context specific input path?
Hey, thanks! I am now the proud owner of a ConTeXt document that
says, "Hello, World!"
I'm going to CC Thomas Esser in case he thinks that others would
benefit from the change.
*** texmf.cnf.dist Mon Apr 5 21:23:26 1999
--- texmf.cnf Tue Sep 7 10:30:59 1999
***************
*** 170,179 ****
TEXINPUTS.omega = .;$TEXMF/{omega,tex}/{plain,generic,}//
% Context macros by Hans Hagen:
! TEXINPUTS.cont-de = .;$TEXMF/{pdftex,tex}/{context,plain,generic,}//
! TEXINPUTS.cont-en = .;$TEXMF/{pdftex,tex}/{context,plain,generic,}//
! TEXINPUTS.cont-nl = .;$TEXMF/{pdftex,tex}/{context,plain,generic,}//
! TEXINPUTS.context = .;$TEXMF/{pdftex,tex}/{context,plain,generic,}//
% odd formats needing their own paths
TEXINPUTS.lamstex = .;$TEXMF/tex/{lamstex,plain,generic,}//
--- 170,179 ----
TEXINPUTS.omega = .;$TEXMF/{omega,tex}/{plain,generic,}//
% Context macros by Hans Hagen:
! TEXINPUTS.cont-de = .;$TEXMF/{pdfetex,pdftex,etex,tex}/{context,plain,generic,
}//
! TEXINPUTS.cont-en = .;$TEXMF/{pdfetex,pdftex,etex,tex}/{context,plain,generic,
}//
! TEXINPUTS.cont-nl = .;$TEXMF/{pdfetex,pdftex,etex,tex}/{context,plain,generic,
}//
! TEXINPUTS.context = .;$TEXMF/{pdfetex,pdftex,etex,tex}/{context,plain,generic,
}//
% odd formats needing their own paths
TEXINPUTS.lamstex = .;$TEXMF/tex/{lamstex,plain,generic,}//
--
--Ed Cashin
ecashin@coe.uga.edu
next prev parent reply other threads:[~1999-09-07 14:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 1:13 seeking ConTeXt code Ed L. Cashin
1999-09-06 19:26 ` Hans Hagen
1999-09-06 20:59 ` RH 6.0 teTeX (was Re: seeking ConTeXt code) (long) Ed L. Cashin
1999-09-07 7:54 ` Hans Hagen
1999-09-07 14:45 ` Ed L. Cashin [this message]
1999-09-08 3:08 ` seeking ConTeXt code Ed L. Cashin
1999-09-08 8:12 ` Hans Hagen
1999-09-09 0:01 ` Ed L. Cashin
1999-09-09 7:23 ` Hans Hagen
1999-09-13 20:33 ` Ed L. Cashin
1999-09-13 23:29 ` Hans Hagen
1999-09-08 8:35 ` Gilbert van den Dobbelsteen
1999-09-08 10:12 ` Hans Hagen
1999-09-09 8:37 ` Tobias Burnus
1999-09-08 12:11 ` Hans Hagen
1999-09-09 0:38 ` Ed L. Cashin
1999-09-09 7:13 ` Hans Hagen
1999-09-10 15:08 ` Ed L. Cashin
1999-09-10 16:13 ` Hans Hagen
1999-09-09 2:45 ` Ed L. Cashin
1999-09-09 7:04 ` Hans Hagen
1999-09-09 9:35 ` Hans Hagen
1999-09-09 9:37 ` Hans Hagen
1999-09-09 18:11 ` Berend de Boer
1999-09-09 10:05 ` Taco Hoekwater
1999-09-09 10:14 ` Taco Hoekwater
1999-09-09 10:26 ` Taco Hoekwater
1999-09-09 11:04 ` Taco Hoekwater
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=vhoso4q2314.fsf@jane.coe.uga.edu \
--to=ecashin@coe.uga.edu \
--cc=ntg-context@ntg.nl \
--cc=te@informatik.uni-hannover.de \
/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).