From: Thomas Fehige <thomas@fehige.de>
To: ntg-context@ntg.nl
Subject: Re: Setting up TeXworks
Date: Tue, 17 May 2016 14:39:27 +0200 [thread overview]
Message-ID: <573B10FF.3030200@fehige.de> (raw)
In-Reply-To: <573AFD89.7070903@fehige.de>
Whew, I've got it running, finally.
For some reason, TeXworks needs to tell mtxrun explicitly where its
texmf-tree is located. Meaning, an additional argument is required in
TeXworks's starter setup, which now looks like this:
name: ConTeXt MkIV
command: mtxrun
arguments:
--tree=/usr/local/context/tex <-- this is the one!
--autogenerate
--script
context
$fullname
In the "Paths to TeX and friends" list I have
/usr/local/context/texmf-linux-64
/usr/local/context/bin
as the top two entries.
I don't know what exactly is going on here, so I don't feel confident to
add this to the wiki, but maybe someone else does and will.
Thanks for listening -- Thomas
Am 17.05.2016 um 13:16 schrieb Thomas Fehige:
> I tried that, no success (not very different from what I did before
> either). Are there other tests that I could do? Can't anybody
> interpret the messages, error and otherwise?
>
> Cheers -- Thomas
>
> Am 16.05.2016 um 17:55 schrieb Jean-Pierre Delange:
>> At the end of this website page
>> http://lesfichesabebert.fr/index.php/Context/Instalation, there are
>> some explanations about the TeXWorks typesetting setting. There are
>> some screen prints which may help.
>>
>> ----- Mail original -----
>> De: "Thomas Fehige" <thomas@fehige.de>
>> À: ntg-context@ntg.nl
>> Envoyé: Lundi 16 Mai 2016 17:46:13
>> Objet: Re: [NTG-context] Setting up TeXworks
>>
>>
>> Am 06.05.2016 um 13:39 schrieb L.S.-Soc&Gam:
>>
>>
>>
>> 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"
>>
>> That I did. Not *.exe though, being on a Linux OS, Xubuntu to be
>> precise.
>>
>>
>>
>> - 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
>>
>> Translating this into Linux, all this works fine.
>>
>>
>>
>> - 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.
>>
>> Thanks for your detailed description, but I'm afraid that's not it.
>> Meanwhile I uninstalled all my texlive packets and reinstalled
>> TeXworks without any of the texlive components, and reinstalled
>> ConTeXt standalone strictly according to this:
>> http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions
>> -- and the problem persists. mtxrun is found and started allright,
>> but it complains that it can't find some files, that a database is
>> outdated, and that it can't find some other files and stops without a
>> pdf. Below is the complete console output as shown in TeXworks.
>> Calling "context test" in a terminal window works fine, though.
>>
>> Cheers -- Thomas
>>
>>
>>
>> ----------------------------------------------------------------------------------
>>
>>
>> mtxrun | forcing cache reload
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path
>> '/usr/local/context/bin' from specification 'selfautoloc:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/share/texmf-local/web2c' from specification
>> 'selfautoloc:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/share/texmf-dist/web2c' from specification
>> 'selfautoloc:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/share/texmf/web2c' from specification
>> 'selfautoloc:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/texmf-local/web2c' from specification
>> 'selfautoloc:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/texmf-dist/web2c' from specification
>> 'selfautoloc:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/texmf/web2c' from specification
>> 'selfautoloc:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path
>> '/usr/local/context' from specification 'selfautodir:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/share/texmf-local/web2c' from specification
>> 'selfautodir:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/share/texmf-dist/web2c' from specification
>> 'selfautodir:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/share/texmf/web2c' from specification
>> 'selfautodir:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/texmf-local/web2c' from specification
>> 'selfautodir:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/texmf-dist/web2c' from specification
>> 'selfautodir:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/texmf/web2c' from specification
>> 'selfautodir:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path
>> '/usr/local' from specification 'selfautoparent:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/share/texmf-local/web2c' from specification
>> 'selfautoparent:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/share/texmf-dist/web2c' from specification
>> 'selfautoparent:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/share/texmf/web2c' from specification
>> 'selfautoparent:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/texmf-local/web2c' from specification
>> 'selfautoparent:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/texmf-dist/web2c' from specification
>> 'selfautoparent:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/texmf/web2c' from specification
>> 'selfautoparent:/texmf/web2c'
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | warning: no lua configuration files found
>>
>> resolvers | resolving | no texmf paths are defined (using TEXMF)
>>
>> resolvers | resolving |
>>
>> mtxrun | the resolver databases are not present or outdated
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-context.lua' using hash
>> 'lua::mtx-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-contexts.lua' using
>> hash 'lua::mtx-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-t-context.lua' using
>> hash 'lua::mtx-t-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-t-contexts.lua' using
>> hash 'lua::mtx-t-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'context.lua' using hash
>> 'lua::context.lua'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path
>> '/usr/local/context/bin' from specification 'selfautoloc:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/share/texmf-local/web2c' from specification
>> 'selfautoloc:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/share/texmf-dist/web2c' from specification
>> 'selfautoloc:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/share/texmf/web2c' from specification
>> 'selfautoloc:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/texmf-local/web2c' from specification
>> 'selfautoloc:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/texmf-dist/web2c' from specification
>> 'selfautoloc:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/bin/texmf/web2c' from specification
>> 'selfautoloc:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path
>> '/usr/local/context' from specification 'selfautodir:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/share/texmf-local/web2c' from specification
>> 'selfautodir:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/share/texmf-dist/web2c' from specification
>> 'selfautodir:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/share/texmf/web2c' from specification
>> 'selfautodir:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/texmf-local/web2c' from specification
>> 'selfautodir:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/texmf-dist/web2c' from specification
>> 'selfautodir:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/context/texmf/web2c' from specification
>> 'selfautodir:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path
>> '/usr/local' from specification 'selfautoparent:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/share/texmf-local/web2c' from specification
>> 'selfautoparent:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/share/texmf-dist/web2c' from specification
>> 'selfautoparent:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/share/texmf/web2c' from specification
>> 'selfautoparent:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/texmf-local/web2c' from specification
>> 'selfautoparent:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/texmf-dist/web2c' from specification
>> 'selfautoparent:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path
>> '/usr/local/texmf/web2c' from specification
>> 'selfautoparent:/texmf/web2c'
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | warning: no lua configuration files found
>>
>> resolvers | resolving | no texmf paths are definedDid (using TEXMF)
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | remembered file 'context.lua'
>>
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
>>
>> ----------------------------------------------------------------------------------
>>
>>
>>
>>
>>
>> ___________________________________________________________________________________
>>
>> 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
>> ___________________________________________________________________________________
>>
>> ___________________________________________________________________________________
>>
>> 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
>> ___________________________________________________________________________________
>>
>
> ___________________________________________________________________________________
>
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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-17 12: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
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 [this message]
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=573B10FF.3030200@fehige.de \
--to=thomas@fehige.de \
--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).