From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Setting up TeXworks
Date: Fri, 6 May 2016 10:04:46 +0200 [thread overview]
Message-ID: <CALBOmsZ_WhY25XZGh_+JnyeRq7FC=Xxgtg-EYd=xSJCZ8uSXcA@mail.gmail.com> (raw)
In-Reply-To: <57286DD6.8050603@fehige.de>
On 3 May 2016 at 11:22, Thomas Fehige wrote:
>
> OK, that helps. Everything is fine from the command line. I seem to be
> overlooking something as to the setup of TeXworks, though. I copied the
> programme calls from the tools.ini that came with the ConTeXt standalone
> version into the present tools.ini that lives in my personal TeXworks config
> folder. Now TW starts mtxrun allright, but the run crashes with
>
> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
Can you check the paths in the fourth tab (= Typesetting) of
Preferences/Settings?
It is possible that you have more than one version of ConTeXt
installed and that you see different paths in the Terminal than in the
GUI.
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-06 8:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 7:10 uppercase, small caps, numerals and German capital sharp s Thomas Fehige
2016-04-19 12:05 ` Wolfgang Schuster
2016-04-19 12:46 ` Thomas Fehige
2016-04-20 14:03 ` Thomas Fehige
2016-04-20 14:25 ` Wolfgang Schuster
2016-04-20 21:25 ` Thomas Fehige
2016-04-20 21:27 ` Thomas Fehige
2016-04-22 11:35 ` glyph substitution Thomas Fehige
2016-04-22 20:28 ` Hans Hagen
2016-04-25 9:53 ` Thomas Fehige
2016-04-25 12:48 ` Thomas Fehige
2016-04-25 15:49 ` Thomas Fehige
2016-04-25 18:12 ` Thomas Fehige
2016-04-25 20:44 ` Wolfgang Schuster
2016-04-26 8:42 ` Thomas Fehige
2016-04-27 14:27 ` Thomas Fehige
2016-04-27 15:10 ` Hans Hagen
2016-04-29 7:44 ` Thomas Fehige
2016-04-29 7:56 ` Hans Hagen
2016-04-29 8:38 ` Test Suite Fonts "extensions-001" Thomas Fehige
2016-04-29 9:05 ` Wolfgang Schuster
2016-05-03 9:22 ` Setting up TeXworks Thomas Fehige
2016-05-06 8:04 ` Mojca Miklavec [this message]
2016-05-06 11:39 ` L.S.-Soc&Gam
2016-05-16 15:46 ` Thomas Fehige
2016-05-16 15:55 ` Jean-Pierre Delange
2016-05-17 11:16 ` Thomas Fehige
2016-05-17 12:39 ` Thomas Fehige
2016-05-17 12:59 ` Hans Hagen
2016-05-19 14:09 ` Thomas Fehige
2016-05-17 13:22 ` Jean-Pierre Delange
2016-05-19 15:16 ` Thomas Fehige
2016-05-19 16:15 ` Jean-Pierre Delange
2016-05-07 10:49 ` Thomas Fehige
2016-05-09 11:02 ` Thomas Fehige
2016-05-15 19:29 ` Thomas Fehige
2016-05-16 14:34 ` ConTeXt and Scite Thomas Fehige
2016-05-03 9:51 ` Setting up TeXworks Thomas Fehige
2016-05-03 10:21 ` Mojca Miklavec
2016-05-03 13:01 ` Thomas Fehige
2016-04-25 20:47 ` glyph substitution Wolfgang Schuster
2016-04-26 7:42 ` Thomas Fehige
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='CALBOmsZ_WhY25XZGh_+JnyeRq7FC=Xxgtg-EYd=xSJCZ8uSXcA@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.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).