Hi! I updated my ConTeXt installation today and now it refuses to work with TextMate and TeXworks. When I use the typesetting command on either editor, I get the error message mtxrun | unknown script 'context.lua' or 'mtx-context.lua' The weird thing is that my ConTeXt standalone installation works on command line (with "context myfile.tex"). I've used TextMate for a year and did not change anything there. Both editors also have my ConTeXt directory /Applications/ConTeXt/tex/texmf-osx-64/bin/context as PATH variable (I got a different error message on TeXworks before I edited the path variable to include ConTeXt). So in theory everything should be fine... I first installed the newest ConTeXt and when it gave the above error message, I switched to latest "stable" version (installation with --context=current), but that didn't make any difference. My previous installation was at least 3 months old, possibly quite a bit older. This problem is not critical as I can use TextMate/TeXworks as editor and compile on command line in Terminal, but it is a bit of a nuisance not to be able to use the typesetting command in the editor. So any help is highly appreciated. Thanks, Mari
Hi Mari,
I use TeXShop. TeXWorks is based on TeXShop.
For ConTeXt Standalone I use:
set path= (/Users/quayjay/context/tex/texmf-osx-64/bin $path /usr/local/bin)
mtxrun --script context --autogenerate --synctex=1 "$1"
This ensures that the environment is setup right.
Hope this helps
regards
Keith.
Am 14.08.2013 um 21:34 schrieb Mari Voipio
Hi!
I updated my ConTeXt installation today and now it refuses to work with TextMate and TeXworks. When I use the typesetting command on either editor, I get the error message
mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
The weird thing is that my ConTeXt standalone installation works on command line (with "context myfile.tex"). I've used TextMate for a year and did not change anything there. Both editors also have my ConTeXt directory /Applications/ConTeXt/tex/texmf-osx-64/bin/context as PATH variable (I got a different error message on TeXworks before I edited the path variable to include ConTeXt). So in theory everything should be fine...
I first installed the newest ConTeXt and when it gave the above error message, I switched to latest "stable" version (installation with --context=current), but that didn't make any difference. My previous installation was at least 3 months old, possibly quite a bit older.
This problem is not critical as I can use TextMate/TeXworks as editor and compile on command line in Terminal, but it is a bit of a nuisance not to be able to use the typesetting command in the editor. So any help is highly appreciated.
Thanks,
Mari ___________________________________________________________________________________ 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 ___________________________________________________________________________________
On 8/14/2013 9:34 PM, Mari Voipio wrote:
Hi!
I updated my ConTeXt installation today and now it refuses to work with TextMate and TeXworks. When I use the typesetting command on either editor, I get the error message
As you come from windows/scite you could try scite on osx. Unfortunately I couldn't figure quit how to use the new context lexers on that platform. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hello,
I think, you should remove the last 'context' in your PATH. So it should be '/Applications/ConTeXt/tex/texmf-osx-64/bin/'.
Jannik
Am 16.08.2013 um 10:06 schrieb Hans Hagen
On 8/14/2013 9:34 PM, Mari Voipio wrote:
Hi!
I updated my ConTeXt installation today and now it refuses to work with TextMate and TeXworks. When I use the typesetting command on either editor, I get the error message
As you come from windows/scite you could try scite on osx. Unfortunately I couldn't figure quit how to use the new context lexers on that platform.
Hans
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ 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 ___________________________________________________________________________________
On Fri, Aug 16, 2013 at 2:10 PM, Jannik Voges
I think, you should remove the last 'context' in your PATH. So it should be '/Applications/ConTeXt/tex/texmf-osx-64/bin/'.
That was a cut-and-paste error, the path was ok. Sharp eyes you have, spotting that, I didn't notice at all! Mari
On Wed, Aug 14, 2013 at 10:34 PM, Mari Voipio
Hi!
I updated my ConTeXt installation today and now it refuses to work with TextMate and TeXworks. When I use the typesetting command on either editor, I get the error message
mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
The weird thing is that my ConTeXt standalone installation works on command line (with "context myfile.tex").
I finally realized that I hadn't tried using ConTeXt from an editor since I installed MacTeX Basic on this computer (the full package refuses to download, even with Safari). So the problem wasn't in the ConTeXt update but in what I did before that. It took a bit of digging, but in a moment of inspiration I checked /usr/ and found a symbolic link texbin -> /Library/TeX/Distributions/.DefaultTeX/Contents/Programs/texbin I *think* that was what wreaked havoc in my editors, because when I _removed_ the texbin path from TextMate, ConTeXt started working again in that editor. So now I have TextMate for ConTeXt and TeXShop for LaTeX, and I'm quite content with this arrangement; I don't mind having dedicated software as long as it works and I've achieved that aim now. Thank you all for your help in deducing that I indeed had a path problem, that led me to find a (the?) solution. Regards, Mari
participants (4)
-
Hans Hagen -
Jannik Voges -
Keith J. Schultz -
Mari Voipio