ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Arnold <darnold@northcoast.com>
Subject: Re: Texexec changing directories
Date: Sun, 24 Aug 2003 22:56:56 -0700	[thread overview]
Message-ID: <3.0.5.32.20030824225656.00b77820@mail.northcoast.com> (raw)
In-Reply-To: <5.2.0.9.1.20030824232528.01234b48@localhost>

Hans,

My path:

C:\WINDOWS\DESKTOP>path
PATH=F:\NLIB;F:\MIKTEX\MIKTEX\BIN;C:\GS\GS7.04\BIN;C:\GS\GS7.04\LIB;F:\MIKTE
X\CO
NTEXT\PERLTK;C:\PERL\BIN;C:\WINDOWS;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\YANDY\Y
ANDY
TEX\;E:\MATLAB6P1\BIN\WIN32;C:\EMACS\BIN;;C:\GHOSTGUM\GSVIEW\;;F:\MSYS\1.0\M
INGW
\BIN;F:\IMAGINE\BIN;;E:\J2SDK1.4.0_02\BIN;E:\MATLAB6P5\BIN\WIN32;F:\SSHSEC~1

However, these are the only instances of texexec.pl and texexec.ini and
texexec.exe on my system, as I removed the versions from miktex\miktex\bin.

F:\miktex\context\perltk>dir texexec*

 Volume in drive F is MICRON
 Volume Serial Number is 075D-1CFB
 Directory of F:\miktex\context\perltk

TEXEXEC  PL         96,117  07-21-03 10:14p texexec.pl
TEXEXEC  RME         5,229  01-31-03 10:05a texexec.rme
TEXEXE~1 INI         5,202  07-29-03 10:47p texexec.ini~
TEXEXEC  INI         5,209  07-29-03 10:57p texexec.ini
TEXEXEC  EXE        20,480  07-13-01 12:06p texexec.exe



At 11:26 PM 8/24/03 +0200, you wrote:
>At 15:46 23/08/2003 -0700, you wrote:
>
>>Note how the drive letter has changed. This is not just a minor annoyance,
>>because if I have a "make" file such as make.bat defined by
>>
>>texexec --pdf --mode=screen --suffix="-s" Context-VecMat
>>texexec --pdf --mode=letter --suffix="-p" Context-VecMat
>>texexec --pdf --mode=screen --suffix="-s" Context-VecMat
>>texexec --pdf --mode=letter --suffix="-p" Context-VecMat
>>
>>After the first run, the process stops because it can no longer find
>>Context-VecMat on the f: partition.
>
>can you fetch version 3.3 from the site so that we are in sync?
>
>there only time when context (when needed) does a change dir (and back) is 
>when it generates formats so ...
>
>is there something funny in your path?
>
>Hans
>
>-------------------------------------------------------------------------
>                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
>                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
>-------------------------------------------------------------------------
>                        information: http://www.pragma-ade.com/roadmap.pdf
>                     documentation: http://www.pragma-ade.com/showcase.pdf
>-------------------------------------------------------------------------
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>

  reply	other threads:[~2003-08-25  5:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 22:46 David Arnold
2003-08-24  3:52 ` Matthew Huggett
2003-08-24  9:59 ` Giuseppe Bilotta
2003-08-25  6:05   ` David Arnold
2003-08-24 21:26 ` Hans Hagen
2003-08-25  5:56   ` David Arnold [this message]
2003-08-28  5:44   ` David Arnold

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=3.0.5.32.20030824225656.00b77820@mail.northcoast.com \
    --to=darnold@northcoast.com \
    --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).