Getting ConTeXt(LuaTeX) option installed /enabled in TeXworks?

Support Software & Applications
1

I was using LaTex in Kile and want to try ConTeXt with LuaTeX engine. It appears that Kile doesn’t process ConTeXt; so, I am trying TeXworks. Under the Typeset drop-down, all the options for ConTeXt appear except “ConTeXt(LuaTeX)”; but LuaTeX appears by itself.

Would you please point me to what I might be missing to get this option available? Thank you.

Or, perhaps, Kile can process ConTeXt or there is another option in addition to TeXworks.

Edited after learning a bit more:
Although I didn’t pursue getting it to work completely, it appears that Kile can process ConTeXt. It appears under the Compile option after installing texlive-context. Also need luametatex if want to use the LMTX version which is the most recent.

However, the PATH needs set to make it work; but I didn’t get it to work in Kile. Instead, I followed the instructions from the pragma ade site and installed it under home, and that provided guidance on how to set the path, and then I just run it from the CLI using “context” as would for any other application. Thus, not using Kile or TeXworks but only Kate as the text editor and running ConTeXt from the CLI.

I suspect (but cannot now demonstrate it) that, if the path is set correctly for ConTeXt and
luametatex, Kile can work with it. The truth is I don’t know enough about setting path variables and the like and have some learning to do there; but the first line below (provided in the output of install.sh) worked for the manual installation under home. But I think more is needed to get luametatex to work in Kile or TeXworks directly.

If you want to run ConTeXt everywhere, you need to adapt the path, like:

 export PATH=/home/gary/data/context/context-linux-64/tex/texmf-linux-64/bin:$PATH

If you run from an editor you can specify the full path to mtxrun:

 /home/gary/data/context/context-linux-64/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context --autopdf ...

These links might also be useful. Appears that if do so through texlive and luametatex, the path and symlinks need set up such that texlive knows where to look for luametatex because of something to do with ConTeXt using cmake and texlive using autotools (over my head, sorry).
https://wiki.contextgarden.net/Introduction/Installation
https://wiki.contextgarden.net/Building_LuaMetaTeX_for_TeX_Live

2

I’ve never used ConteXt.

ConteXt is only coincidentally the name of this application – ConteXt (LuaTeX) is one of the actual typesets that the name was derived from – any similarity of the name is of no real consequence.

I used Kile for a (very) short time, but found it lacking – TeXworks, however, is my personal goto for most things LateX.

You can select from LuaTeX, LuaLateX, ConteXt (LuaTeX), ConteXt (pdfTeX), or pdfLateX via the dropdown (top, left).

ConteXt (LuaTeX) is a separate typeset – you use any of them, but they are all still subsets of LateX, albeit with different characteristics, or features, if you will. I personally favour LuaLateX because it has the support needed/desired for an ongoing project I’m working on currently.

For those unfamiliar with LateX generally, they are at a distinct disadvantage as there is much information available (an Internet search away) but most will only reference one of these flavours of LateX.

You need to decide for yourself which typeset will suit your needs, on a case by case basis. I’m afraid there are few shortcuts for the uninitiated. I’ve been using LateX (off and on) for many years, and I find a favourite Search engine is still my best friend for discovering how to use the syntax required for each typeset, in any given circumstance.

I hope this helps in some way.

Regards.

3

Thank you. I just figured it out, though “figured” is too strong a word. I was reading about ConTeXt on the developer’s site pragma-ade.com and, although not sure I understand it correctly, once I installed luametatex and restarrted TeXworks, the Typset of ConTeXt(luaTeX) is now enabled/selectable.

I read that the engine(s) in the MKII version (PDFTEX and XETEX) have been frozen apart from bug fixes; and the MKIV version that uses LUATEX gets changed only slightly; and the LMTX version that uses LUAMETATEX is the version that is developed.

I don’t know which version TeXworks uses for ConTeXt, but once luametatex was installed that Typeset selection is enabled.

you use any of them, but they are all still subsets of LateX

I didn’t understand it this way; but may be wrong, of course. My understanding (only from reading the past two days, including an interview of it’s creator Hans Hagen and his introduction to it and its differences from LaTeX) is that it uses the TeX engine underneath but differs from LaTeX in that one doesn’t need all those LaTeX packages (much/most of that is built in) and it is closer to coding in plain TeX, though made easier for the user.

I’ve yet to try it, but was told by the individual suggesting it to me that “it will give you a much more coherent environment to build things in”; because my struggle with LaTeX is that I just use trial and error on its many packages until I get the layout I need but without ever really understanding what those packages are doing; and hope that they don’t clash/conflict. The main issue is that I simply do not know enough about LaTeX or TeX. I have the two volumes of The LaTeX Companion and a couple binders full of the individual package’s documentation, use them in my preambles but still have no clue how they work. Building/styling a TOC, for example, I found to be quite challenging.

4

Ah, a traditionalist. :crossed_fingers:

That’s always a problem that each successive implementation has tried to solve, in it’s own way.

To me, it reminds me of standards:

Q: What happens if a new standard is designed to replace 10 existing standards?
A: You have 11 existing standards.

1 Like