From: Hans Hagen <pragma@wxs.nl>
Subject: Re: How do Windows users call texexec etc.
Date: Thu, 09 Jun 2005 21:58:44 +0200 [thread overview]
Message-ID: <42A89F74.9070107@wxs.nl> (raw)
In-Reply-To: <200506091527.58426.john@wexfordpress.com>
John R. Culleton wrote:
> I have been using Linux since the days of Win 3.1. So I don't
> know what goes on in the MSWin world any more.
>
> Specifically I am writing a guide for typesetting beginners. What
> should I tell them is a good way to execute e.g., texexec from a
> Windows environment? Many of them are afraid of the command
> line. My instinct is to describe a Vim command such as
> :!texexec %
> or just give them a script to do that, but there may be a better
> alternative. Thoughts?
given that texmfstart.exe is in you binary path (there is a zip on our website,
else you need to install ruby, associate .rb with calling ruby, and use
texmfstart.rb)
texmfstart texexec ...
you can also run
texmfstart --make texexec.pl
which will give you a stub 'texexec.bat' which you can then put in your path
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-06-09 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 15:27 John R. Culleton
2005-06-09 19:58 ` Hans Hagen [this message]
2005-06-09 21:02 ` Steve Peter
2005-06-09 21:05 ` Willi Egger
2005-06-09 19:43 ` John R. Culleton
2005-06-10 7:43 ` Hans Hagen
2005-06-10 21:04 ` Willi Egger
[not found] <20050610061421.79FAA1280F@ronja.ntg.nl>
2005-06-10 7:39 ` Roef Ragas
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=42A89F74.9070107@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.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).