From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/426 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: I've got a decent start, but ... Date: Wed, 19 May 1999 10:53:56 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <37427C24.87D245BD@wxs.nl> References: <3.0.5.32.19990518233310.00a8a100@mail.northcoast.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035391286 23957 80.91.224.250 (23 Oct 2002 16:41:26 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:41:26 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: David Arnold Xref: main.gmane.org gmane.comp.tex.context:426 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:426 David Arnold wrote: > OK, Win95, Miktex, and WinEdt. That's my configuration. > > 1. I got the file dcom95.exe and installed it. That seemed to go well, > asking to restart the computer. All OK so far. > > 2. I got APi516e.exe (Active Perl) and installed. All seemed to go well. I > simply selected defaults all the way during the installation. I told the > installation to adapt my autoexec.bat. I selected restart the computer when > the installation finished. > > 3. I unzipped cont-tmf.zip into the texmf directory tree. I kept precisely > the same directory structure used in cont-tmf.zip. That seemed to go well. > > Now, how to proceed from here? > > I could make a Context button in WinEdt, then put the appropriate file to > call in winedt\bin, and set the command line to call that file. But which > file? What is the best way to proceed? And should I make a format file? you could make a batch file that runs texexec. You first need to put texexec.pl somewhere in your path. When 'texexec' runs, its ok. Fabrice made a perl script launcher, I'll send that one in a separate mail; just copy it to texexec.exe and put it in the same path as texexec.pl . Another way of launching texexec from the prompt is 'start texexec.pl' You need to adapt texexec.ini to your local situation. Take a look at the 'pragma' section, copy it and add your own changes. Enable that section. Texexec.ini should be in the same path as texexec.pl (I assume you don't have kpathseawhich cum suis running). You need to be able to run texexec --make en or perl texexec --make en for the english format. texexec or perl texexec processes the file. These can go under a button winedt I suppose. (texexec runs the file as many times as needed, calls texutil to sort the index and some lists) 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.nl -----------------------------------------------------------------