Alex Lubberts wrote:

Hi,

Yesterday I wanted to try out texworks for editing and typesetting my context documents. I installed texworks from the ubuntu launchpad ppa since '--goodies=texworks' doesn't work on linux-64, yet.

Then I ran into a few problems:

* The script mtx-texworks.lua wasn't able to start texworks because "unable to locate texworks". In the loop that's searching all the binpaths I put in 'logs.simple("%s",p)' and found out that binpaths only consists of one element: the complete PATH variable. I guess it means that there's something wrong with the function file.split_path, but I don't understand what's happening there. When I replaced the loop with 'p="/usr/bin/texworks"' texworks started as expected.

hm, strange, but just patching the file.split_path function is kin dof dangerous .. mayb the path separator is not identified well

* However the typesetting engines were not correctly set up. Texworks (at least on linux) seems to be looking for a file TeXworks.ini. The one in the minimals distribution is called texworks.ini. Renaming this solved it...

has to do with the fact that these are user prefs and stored in a system dependent way (only windows can be configured); this will chang ein future versions of texworks

* ... almost. In the TeXworks.ini file I also had to replace all occurunces of 'mtxrun.cmd' (doesn't work on linux, is this correct for Windows?) with 'mtxrun'.

needs testing

I wish I could help solve these points, but since I'm not much of a programmer I cannot solve the first issue, and the other are just a matter of renaming/replacing??

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 -----------------------------------------------------------------