From: ishamid <ishamid@lamar.colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: RE: automating initialization
Date: Thu, 17 Mar 2005 08:26:56 -0700 [thread overview]
Message-ID: <423A8EEE@webmail.colostate.edu> (raw)
>===== Original Message From Hans Hagen <pragma@wxs.nl> =====
>ishamid wrote:
>> Dear gang,
>>
>> How do I automate initialization of the separate context tree (from
>> mswintex.zip)? A simple batch file such as
>>
>> ========================================
>> setuptex c:\context
>> texexec foo
>> ========================================
>>
>> does not work; the batch file always turns itself off before texexec can be
>> invoked. Can I make the initialization global so that all batch files (such
as
>> those called by WinEDT) will work properly? I added c:\context to the path
but
>> that is not enough.
>>
>> BTW: Can initialization be turned off as well?
>
>you can associate batch files to a cmd window, (open action);
can you give me an example?
>in winedt you
>shoul dadd the lines to their bat files (or ask the author to provide an
>initialization option)
Well, the following seems to work for now:
========================================
call setuptex c:\context
texexec foo
========================================
I am pretty ignorant of DOS but <call> seems to solve the problem for now. Now
my WinEDT batch files for pdfetex and aleph can work.
Best
Idris
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-03-17 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 15:26 ishamid [this message]
2005-03-17 16:22 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2005-03-17 3:50 ishamid
2005-03-17 9:40 ` Hans Hagen
2005-03-17 15:10 ` Peter Rolf
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=423A8EEE@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).