From: Hans Hagen <pragma@wxs.nl>
Subject: Re: texexec.ini not read
Date: Wed, 01 Mar 2006 10:40:24 +0100 [thread overview]
Message-ID: <44056C08.8020705@wxs.nl> (raw)
In-Reply-To: <Pine.WNT.4.63.0603010108570.3896@nqvgln>
Aditya Mahajan wrote:
> Oops, forgot to attach the logs
>
> <--- On Mar 1, Aditya Mahajan wrote --->
>
>> <--- On Feb 28, Aditya Mahajan wrote --->
>>
>>> I was trying to make the stand along context work with cygwin using
>>> cygwin ruby. Following the advice on the wiki of adding
>>> /scripts/context/ruby to rubylib, everything works fine. However, I am
>>> not able to enable write18. I copied texexec.rme to texexec.ini and
>>> added -shell-escape to all set TeXPassString in texexec.ini. However,
>>> I still get
>>>
>>> system(mpost .....) disabled
>>>
>>> in my log file. Reading through newtexexec.rb it seems that it does
>>> not check the ini file. Is this correct? Or am I missing something.
>>
>> Strange. If I run the command for dos command prompt, I get
>> system (mpost .....) executed
>>
>> It seems that texexec is looking at different profiles under cygwin.
>> Or rather, for some reason texexec can not find the correct file in
>> cygwin. I am attaching both log files. There is not much difference
>> there.
>>
>> It seems that I still need to work with cmd rather than bash :-(
>> Any hints will be appreciated.
>>
did you enable write 18 in texmf.cnf?
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:[~2006-03-01 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 2:25 Aditya Mahajan
2006-03-01 6:08 ` Aditya Mahajan
2006-03-01 6:09 ` Aditya Mahajan
2006-03-01 9:40 ` Hans Hagen [this message]
2006-03-01 10:25 ` Aditya Mahajan
2006-03-01 9:38 ` 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=44056C08.8020705@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).