gulliet@rutile.enet.dec.com (01/15/91)
Hi,
I have just upload TeX 3.1 from atari.archive.umich.edu.
When I try to run it, it complains that it doesn't find
the plain file (TeX and plain.fmt are together in the same
folder, D:\tex).
How can I define the environment variables, like TEXINPUTS,
within GULAM ? The very short documentation says:
setenv TEXINPUTS ./:/dev/D/tex/texinput (!)
Regards,
/Jean_marc.jvt@its.bt.co.uk (John Trickey) (01/15/91)
In article <18926@shlump.nac.dec.com> gulliet@rutile.enet.dec.com writes: > >When I try to run it, it complains that it doesn't find >the plain file (TeX and plain.fmt are together in the same >folder, D:\tex). > >How can I define the environment variables, like TEXINPUTS, >within GULAM ? The very short documentation says: > > setenv TEXINPUTS ./:/dev/D/tex/texinput (!) Gulam (or Mupfel for those using Gemini) will not like that as the : cannot be used as a separator. Also / is not understood in TOS. Assuming your files are D:\tex\* then you use the command setenv TEXINPUTS .,d:\tex or setenv TEXINPUTS ".;d:\tex" Note the " in the second form to avoid the ; being taken as a command separator. A method I prefer is to set the environment independantly of the shell I use. The prog is environ.prg which must be in \auto and the data file is \environ.dat . In the data file I place (amongst others) TEXINPUTS=.;d:\tex environ is available on most archives. John. -- John Trickey <jvt@its.bt.co.uk> || ..!mcsun!ukc!axion!its G4REV @ GB7SUT Voice: +44 21 333 3369 #include <std/disclaimer>
david@doe.utoronto.ca (David Megginson) (01/16/91)
In article <AX2^58-@uzi-9mm.fulcrum.bt.co.uk> jvt@its.bt.co.uk (John Trickey) writes: >>within GULAM ? The very short documentation says: >> >> setenv TEXINPUTS ./:/dev/D/tex/texinput (!) > >Gulam (or Mupfel for those using Gemini) will not like that >as the : cannot be used as a separator. Also / is not understood >in TOS. Assuming your files are D:\tex\* then you use the command > > setenv TEXINPUTS .,d:\tex > or > setenv TEXINPUTS ".;d:\tex" > >Note the " in the second form to avoid the ; being taken as a command >separator. Actually, it doesn't matter _what_ shell you are using, you should use the form with the forward slashes and colon as separator. That is because it is not the shell, but TeX which will interpret the contents of the variable, and the new TeX binaries want the paths in UNIXMODE format, and with colons as separators. Therefore setenv TEXINPUTS ".:/dev/D/tex" would be correct under any shell (which uses setenv). Hope this isn't too confusing... David -- //////////////////////////////////////////////////////////////////////// / David Megginson david@doe.utoronto.ca / / Centre for Medieval Studies meggin@vm.epas.utoronto.ca / ////////////////////////////////////////////////////////////////////////
ridderbusch.kd@nixdorf.com (Frank Ridderbusch, D10 PU222) (01/17/91)
>>>>> On 14 Jan 91 20:15:04 GMT, gulliet@rutile.enet.dec.com said:
/Jean_marc> Hi,
/Jean_marc> I have just upload TeX 3.1 from atari.archive.umich.edu.
/Jean_marc> When I try to run it, it complains that it doesn't find
/Jean_marc> the plain file (TeX and plain.fmt are together in the same
/Jean_marc> folder, D:\tex).
/Jean_marc> How can I define the environment variables, like TEXINPUTS,
/Jean_marc> within GULAM ? The very short documentation says:
/Jean_marc> setenv TEXINPUTS ./:/dev/D/tex/texinput (!)
/Jean_marc> Regards,
/Jean_marc> /Jean_marc.
There is a file at the atari archive at terminator in the TeX
directory called 'manpages.lzh'. This file contain manual pages
for TeX, Metafont and the other utility programs. The environment
variables are described there.
TeX knows about the four following environment variables (examples are
for gulam):
TEXFONTS
All font metric files (*.TFM) are searched in the directory
described by this variable.
ex: setenv TEXFONTS /dev/F/tex/texinput/tfm
TEXINPUTS
All TeX input and macro files are searched along the paths in
this variable.
ex: setenv TEXINPUTS .:/dev/F/tex/texinput/latyex/styles
TEXFORMATS
TeX loads the dumped format files (*.FMT) from this directory.
ex: setenv TEXFORMATS /dev/F/tex/formats
TEXPOOL
TeX loads the string pool file (TEX.POO) from this directory.
ex: setenv TEXPOOL /dev/F/tex
There are two noteworthy points about the examples.
1.) The use of the ':' as a path separator. This is due to the fact,
that the currently available binaries are the product of a quick
and dirty port to the ST from the Un*x sources. This also disables
the usual partition specifications like 'D:'
2.) The use of a '/dev/<partition>' notation. This is a feature of the
C library, which J.R.Bammi and E.R.Smith put together for GNU-C
on the ST. The code in this library maps the '/dev' notation to
TOS format before calling the actual system call.
I've currently produced new binaries, which now use the ';' as a path
separator and therefore allow the standard TOS notation for pathnames.
Also the new binaries don't discard *any* <CR> characters in the input
stream, but only the ones in a <CR><NL> pair. Also these binaries were
compiled with GCC 1.38 and maximum optimization.
I would be happy to submit these files to the atari archive at
terminator, if someone tells me the correct address for submissions by
mail.
I've also put archives together, which contains the C sources, which
were produced by the conversion process from WEB to C. These sources
may then be used the recompile TeX with differing internal buffer
sizes. (It is possible to compile TeX and Metafont on a ST with GNU-C,
but you need at least 2 megs for TeX and 2.5 megs for Metafont. The
compilation process takes about 1 hour).
--
MfG/Regards
/==== Siemens Nixdorf Informationssysteme AG
/ Ridderbusch / , Abt.: D10 PU222
/ /./ Heinz Nixdorf Ring
/=== /,== ,===/ /,==, // W-4790 Paderborn, Germany
/ // / / // / / \ NERV:ridderbusch.kd
/ / `==/\ / / / \ BTX:0525467066-0001
Email: ridderbusch.kd@nixdorf.com (America (North & South))
ridderbusch.kd@sni.de (Rest of world)
jvt@its.bt.co.uk (John Trickey) (01/18/91)
In article <1991Jan16.031701.3487@doe.utoronto.ca> david@doe.utoronto.ca (David Megginson) writes: > >Actually, it doesn't matter _what_ shell you are using, you should use >the form with the forward slashes and colon as separator. That is because >it is not the shell, but TeX which will interpret the contents of the >variable, and the new TeX binaries want the paths in UNIXMODE format, >and with colons as separators. Therefore > > setenv TEXINPUTS ".:/dev/D/tex" > >would be correct under any shell (which uses setenv). > >Hope this isn't too confusing... Thats *wonderful* news :-( So how do you cope with your source on one partition and your system on another without cd'ing to the system partition? John -- John Trickey <jvt@its.bt.co.uk> || ..!mcsun!ukc!axion!its G4REV @ GB7SUT Voice: +44 21 333 3369 #include <std/disclaimer>
david@doe.utoronto.ca (David Megginson) (01/19/91)
In article <*J4^P`#@uzi-9mm.fulcrum.bt.co.uk> jvt@its.bt.co.uk (John Trickey) writes: >Thats *wonderful* news :-( So how do you cope with your source on one >partition and your system on another without cd'ing to the system partition? I'm sorry for not making it clearer. In this system, /dev/<letter> is the way of specifying a disk drive. For example, termcap (should) take any value for the environment variable TERMCAP beginning with a slash as a pathname, and any other value as an actual termcap entry. If you keep your termcap database in e:\etc, try setenv TERMCAP /dev/E/etc/termcap I hope that this makes it clearer to everyone. David -- //////////////////////////////////////////////////////////////////////// / David Megginson david@doe.utoronto.ca / / Centre for Medieval Studies meggin@vm.epas.utoronto.ca / ////////////////////////////////////////////////////////////////////////
tony@tacky.cs.olemiss.edu (Tony Reynolds) (01/22/91)
I downloaded all the .lzh files from the terminator archive.
I de-lzhed em all, putting together what seemed like a reasonable
directory tree for the files, given the README file included with
TeX and Metafont.
Various attempts at running TeX with the Mark William's Shell <msh>,
PCOMMAND, etc. reduced my elation at having TeX on my 1040 to maddness
at myself for bothering to download.
It seems the only way I can run TeX is to turn off my hard-drive and
run it from my floppy. I even reduced my FOLDRXXX to about 10 extra
folders and took out all my accessories and it still would only run
from the desktop. Of course I can't set the environment from the
desktop, so that is a non-solution.
By the way, my setup is as follows:
TOS 1.0, 1040 1MB, SH204 running HDX3.01, and various AUTO
folder programs enabled or disabled at any given time.
Is it just me or do I have an <obsolete |:) > 1040ST?
How about an earlier version of TeX, with a listing of the files
one needs to grab in order to get a working setup?
PLEASE! HELP! I've had a hardcover TeXbook for 3 years and want
to use it!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Please note! All mail directed to me should be sent to my new address:
cctony@4dsci1.ocis.olemiss.edu Thank-you very much.
This includes USENET Mail, please check the "To:" field for replys