ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "L.S.-Soc&Gam" <axteffekt@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Setting up TeXworks
Date: Fri, 6 May 2016 13:39:10 +0200	[thread overview]
Message-ID: <572C825E.90900@gmail.com> (raw)
In-Reply-To: <CALBOmsZ_WhY25XZGh_+JnyeRq7FC=Xxgtg-EYd=xSJCZ8uSXcA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4100 bytes --]



Am 06.05.2016 um 10:04 schrieb Mojca Miklavec:
> 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
> ___________________________________________________________________________________

I've searched through the mailing list, what the initial post to this 
topic was, but i couldn't find it. If you're having trouble to make 
context compile a document, try this:

- TeXworks tools.ini doesn't need to be edited manually. It's the file 
where TW saves the settings from " Edit -> Preferences -> Typesetting ".
- First of all make sure, that you downloaded ConTeXt by using 
"first-setup.exe"

- Then, you should add the folder where context.exe (and all 
executables) are stored to your system paths: Use your browser to 
navigate to the said folder, click on the address bar and copy the full 
path. For me it looks like this: " F:\Sandbox\ConTeXt\tex\texmf-win64\bin "
- Then add this path to your windows system paths: go to your windows 
control panel, double click " System "-> advanced settings -> 
environment variables (or something like this), in the lower halfth 
there is a window with a point " Path ". Double click it and paste your 
CTX folder pretty much at the top of the section or if there is only one 
line, add it at the beginning, and use semikolon ( ; ) to seperate it 
from the rest. Save your settings and you should be good to go.
- to test if you did it correctly open your command line and simply 
enter " context.exe --version ". If command line tells you, that no 
context.exe was found, then you might try to add the context \bin folder 
to your system paths again
- if command line tells you the version of context, then you can proceed:

- start TW, " Edit -> Preferences -> Typesetting ". There check the 
upper halfth for the context folder you added to your system paths. If 
you've added it at the beginning, it should be at the top here as well. 
Alternatively use the arrows to push context\bin it to the very top

NOTE: this is important. if you have MikTeX installed for example and if 
its folder is listed above your context folder, TW will try to use exe 
files from the MikTeX folder. so make sure that context\bin is above 
anything related to tex, context or lua.

- then in the lower halfth create a new processing tool by clikcking on 
the plus:

- call it CTX mkiv or something
- in the program field either search for your context.exe, or if added 
to the system paths correctly, simply enter context.exe in the Program field
- for arguments add:        $fullname                (this parses the 
filename to context compiler)
- if you want to use the sync code <-> pdf feature, also add another 
argument:        --synctex=-1

that's it. there is the option to make this the default profile at the 
bottom of the Typesetting window.

Now you can test it: paste

\starttext
Hello World!
\stoptext

into a new file and save it somewhere. then use your freshly set up 
processing tool. after compilation the pdf viewer should pop up.


I hope that helps, Seba

[-- Attachment #1.2: Type: text/html, Size: 6090 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

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

  reply	other threads:[~2016-05-06 11:39 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
2016-05-06 11:39                             ` L.S.-Soc&Gam [this message]
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=572C825E.90900@gmail.com \
    --to=axteffekt@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).