From: fg@fgbbs.iaf.nl (Frans Goddijn)
Subject: texutil
Date: 12 Aug 98 15:33:01 +0100 [thread overview]
Message-ID: <3c1_9808121539@fgbbs.iaf.nl> (raw)
When calling the texutil.pl instead of the texutil.exe is there a
difference in the way parameters must be given?
This morning I got my PERL5 working under DOS (I had only used it under
OS/2 so far) and I tried the texutil.pl without error but also without
result:
perl5 f:\context\texutil.pl dekunst /references
( perl5 = the executable
f:\context\texutil.pl = the texutil perl sript
dekunst = is dekunst.tex = the file being compiled
/references = the parameter that worked with texutil.exe )
it seems this doesn't create the table of contents like the texutil.exe
used to do.
Met hartelijke groet!
Frans Goddijn | bbs: +31 (0)26 3217041
Postbus 30196 | email: fg@fgbbs.iaf.nl
6803 AD Arnhem | tel: +31 (0)26 3219342
The Netherlands | http://www.iaf.nl/Users/Meridian
--
You are what you is
next reply other threads:[~1998-08-12 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-12 14:33 Frans Goddijn [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 16:00 Texutil Willi Egger
2004-01-13 13:38 ` Texutil Hans Hagen
1998-06-22 8:22 texutil Hans Hagen
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=3c1_9808121539@fgbbs.iaf.nl \
--to=fg@fgbbs.iaf.nl \
/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).