TeXworks or TeXItEasy as ConTeXt editors
Dear list, I’m writing an introduction to ConTeXt in Spanish. Before any new user can start compiling ConTeXt sources, I realize that I have to explain how to configure an editor for ConTeXt. Since I plan to deal with the latest beta from the ConTeXt Suite, I need to explain how to deploy it. I use Geany in Linux and Notepad++ in Windows. But they are too complex for newbies. TeXworks seems the best option to start with (and to explain to newcomers). I compile my documents with the following commands: source ~/context/tex/setuptex && contextjit document.tex I had never problems with that. But as soon as I started to test Qt applications, I cannot use this. I mean, the commands above don’t work either with TeXworks or TexitEasy. Does anyone know how to make the previous commands work with TeXworks? Setting paths is something I want to avoid, since it is potentially dangerous for newbies. Many thanks for your help, Pablo -- http://www.ousia.tk
Hi Pablo,
I’m writing an introduction to ConTeXt in Spanish.
Great initiative!
Does anyone know how to make the previous commands work with TeXworks?
Not off the top of my head; you’ll probably find more help on the TeXworks list (http://tug.org/mailman/listinfo/texworks), I’m sure I’ve seen this question discussed before. I think it’s as simple as putting the command in question in a small script file that you place in TeXworks’ configuration directory. I agree that TeXworks is probably on the best choices for newcomers.
Setting paths is something I want to avoid, since it is potentially dangerous for newbies.
It really shouldn’t be necessary. Best, Arthur
On 08/05/2017 01:50 PM, Arthur Reutenauer wrote:
Does anyone know how to make the previous commands work with TeXworks?
Not off the top of my head; you’ll probably find more help on the TeXworks list (http://tug.org/mailman/listinfo/texworks), I’m sure I’ve seen this question discussed before. I think it’s as simple as putting the command in question in a small script file that you place in TeXworks’ configuration directory.
Hi Arthur, I opened an issue on this topic at GitHub, but I didn’t know there were a mailing list. I have just subscribed to the list, but it seems I have to wait for moderation ;-). I read in the wiki (at GitHub) that adding a script could be an option. But this would be an option for me. Not for a newbie. I mean, I wouldn’t mind to add the script in a computer for a friend. But I would do that myself. Otherwise, it doesn’t have to be dangerous, but it would be extremely hard for people without previous experience.
I agree that TeXworks is probably on the best choices for newcomers.
On the top of the feature that TeXworks is newcomers-friendly, it has also been designed with ConTeXt in mind. One of the weirdest things in the TeX world can be summarized in a single question: why do we say TeX when we only mean LaTeX? Many thanks for your help, Pablo -- http://www.ousia.tk
Hi Pablo,
I use to work (to compile) on ConTeXt documents only with TeXworks (on Linux and Windows). Then I guess you're much more able to work with TeXWork than me ! It's very useful and it allows double windows simultaneously : on left your ctx code, on right the pdf output.
You only have to configure two things : the path where texworks finds context executable (~/home/context/tex/texmf-linux32/bin or /.../linux64/bin, and the same for Microsoft Windows). And a to give a little parameter to TeXworks.
I am afraid that you have to read my French explanation here : https://fr.wikibooks.org/wiki/ConTeXt#Installation_et_configuration_de_TeXWo...
But I translate the most important (point 3 of the link given above):
When TeXworks is open, go to "Typesetting/Composition" within the "Edition =>Preferences" menu.
The inferior table "Processing Tools", just create a new tool by clicking on "+" and write "ConTeXt MKIV". In the field "Program", give the path to "context.exe", the same given above. Inside the mask "Arguments" add "$fullname" AND THAT'S ALL ! (Now you are under TeXworks : you must have "ConTeXt MKIV" just beside the green arrow. If your compilation doesn't work maybe it is because you are trying to compile your *.tex file with another executable (pdftex, pdflatex, or anything else...).
Very good idea to build some Spanish documentation on ConTeXt !
Hope it may helps !
JP
----- Mail original -----
De: "Pablo Rodriguez"
On 08/05/2017 03:36 PM, Jean-Pierre Delange wrote:
[...] You only have to configure two things : the path where texworks finds context executable (~/home/context/tex/texmf-linux32/bin or /.../linux64/bin, and the same for Microsoft Windows). And a to give a little parameter to TeXworks. Many thanks for your explanation, Jean-Pierre.
I have tried to set it up before, but with the wrong path to binaries. I thought they were located in the ~/context/bin directory, when they actually were located in the ~/context/tex/texmf-linux/bin directory. Everything works now as expected. Many thanks for your help, Pablo -- http://www.ousia.tk
Hi Pablo,
Indeed, TeXworks setting parameters for the first time is unclear for those who don't know where is ConTeXt executable :
Linux : /home/user/context/tex/texmf-linux/bin is not the first place where one is looking for an executable file;
it's only clearer when we understand that it is the place of most ConTeXt executable files (see below Windows's CTX executables) :
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-multibyte-l1-1-0.dll
api-ms-win-crt-process-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-utility-l1-1-0.dll
bibtex.exe
context.exe
contextjit.exe
ctxtools.exe
dvipos.exe
dvitomp.exe
fc-cache.exe
fc-list.exe
fc-pattern.exe
fc-query.exe
fc-scan.exe
fc-validate.exe
icudt58.dll
icudt59.dll
kpathsea620w64.dll
kpathsea622w64.dll
kpathsea623w64.dll
kpseaccess.exe
kpsestat.exe
kpsewhich.exe
lua.exe
lua52w64.dll
luac.exe
luajit51w64.dll
luajittex.dll
luajittex.exe
luatex-plain.exe
luatex.dll
luatex.exe
luatools.exe
metatex.exe
mktexlsr.exe
mpost.dll
mpost.exe
mptopdf.exe
msvcp140.dll
msvcr100.dll
mtxrun.dll
mtxrun.exe
mtxrun.lua
mtxrunjit.exe
pdftex.dll
pdftex.exe
pltotf.exe
pstopdf.exe
texexec.exe
texlua.exe
texluac.exe
texluajit.exe
texluajitc.exe
texmfstart.exe
tftopl.exe
vcruntime140.dll
vftovp.exe
vptovf.exe
xdvipdfmx.exe
xetex.exe
----- Mail original -----
De: "Pablo Rodriguez"
[...] You only have to configure two things : the path where texworks finds context executable (~/home/context/tex/texmf-linux32/bin or /.../linux64/bin, and the same for Microsoft Windows). And a to give a little parameter to TeXworks. Many thanks for your explanation, Jean-Pierre.
I have tried to set it up before, but with the wrong path to binaries. I thought they were located in the ~/context/bin directory, when they actually were located in the ~/context/tex/texmf-linux/bin directory. Everything works now as expected. Many thanks for your help, Pablo -- http://www.ousia.tk ___________________________________________________________________________________ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
participants (3)
-
Arthur Reutenauer -
Jean-Pierre Delange -
Pablo Rodriguez