- ntg-context - NTG Mailing Lists

Can not update Context Standalone
by Fabrice Couvreur 08 Apr '19

08 Apr '19

Hi, I have just updated context standalone and I get the following errors : When you want to use context, you need to initialize the tree by typing: . /home/viserion/context/tex/setuptex in your shell or add "/home/viserion/context/tex/texmf-linux-64/bin" to PATH variable if you want to set it permanently. This can usually be done in .bashrc, .bash_profile (or whatever file is used to initialize your shell). [viserion@archlinux context]$ mtxrun --generate bash: /home/viserion/bin/mtxrun: Aucun fichier ou dossier de ce type [viserion@archlinux context]$ context --make /home/viserion/texlive/2018/bin/x86_64-linux/context: ligne 2: /home/viserion/bin/mtxrun: Aucun fichier ou dossier de ce type [viserion@archlinux context]$ Thanks Fabrice

1 1

luametatex : command not found
by Fabrice Couvreur 08 Apr '19

08 Apr '19

Hi, My system is unix and my platform is linux-64. I installed ConTeXt LMTX as described, namely in my home and in the directory /data /context/ I then tried to compile but without success a file : [viserion@archlinux ~]$ /home/viserion/data/context/tex/texmf-linux-64/bin/context area.tex mtx-context | run 1: luametatex --fmt="/home/viserion/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en" --jobname="area" --lua="/home/viserion/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui" --c:currentrun=1 --c:fulljobname="./area.tex" --c:input="./area.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/home/viserion/data/context/tex/texmf-linux-64/bin" "cont-yes.mkiv" sh: luametatex : commande introuvable mtx-context | fatal error: return code: 32512 [viserion@archlinux ~]$ Thanks Fabrice

2 3

Re: [NTG-context] follow up
by Jeong Dal 08 Apr '19

08 Apr '19

Dear Hans and Otared, Thank you for your help. It is OK to use ConTeXt-LMTX in TeXShop and in Atom. I’d like to compile it in LMTX mode or in MKIV mode without running "mtxrun —geneate” when I change mode. Set path to absolute path of mtxrun in the setting doesn’t help. Actually, it is not a problem of ConTeXt. I’ll try it once more. Thank you. Best regards, Dalyoung > 2019. 4. 5. 오후 7:00, ntg-context-request(a)ntg.nl 작성: > > Send ntg-context mailing list submissions to > ntg-context(a)ntg.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ntg.nl/mailman/listinfo/ntg-context > or, via email, send a message with subject or body 'help' to > ntg-context-request(a)ntg.nl > > You can reach the person managing the list at > ntg-context-owner(a)ntg.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ntg-context digest..." > > > Today's Topics: > > 1. Re: How to update LMTX? (Hans Hagen) > 2. Re: follow up (Hans Hagen) > 3. Re: (no subject) (Hans Hagen) > 4. Re: follow up (Otared Kavian) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Apr 2019 00:20:32 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] How to update LMTX? > Message-ID: <4ab6b1ec-62cd-90c8-0f54-b303f025c2b6(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 4/5/2019 12:09 AM, Alan Braslau wrote: >> On Thu, 4 Apr 2019 23:11:42 +0200 >> Hans Hagen <j.hagen(a)xs4all.nl> wrote: >> >>> (we just don't use rsync) >> >> As rsync can be problematic for some locations >> (TCP port 873 blocked) without the ability to >> tunnel. > > indeed, especially in schools > >> http is most often open. > right and rsync is also very unix centric so on windows one has to use > cygwin (bah) or a mingw version (hard to get); also the rsync protocol > is sometimes updated so then you need matching versions > > Hans > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- > > > ------------------------------ > > Message: 2 > Date: Fri, 5 Apr 2019 00:28:19 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] follow up > Message-ID: <8f908232-5516-b2a7-df76-51eba0c5140e(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 4/5/2019 12:17 AM, Jeong Dal wrote: >> Dear Hans, >> >> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side. >> But I have a problem to run it. >> >> If it is OK to run a file in LMTX environment, then I got a following >> error when I run it in MKIV environment. >> “I can’t fine a file …../defFonts.tex” even though it is there. >> To resolve it, I run “mtxrun —generate” in MKIV. >> But it invoke the same type error in LMTX. >> Here are the command in Atom editor which I use to run it. >> >> LMTX: >> source /Users/graph/ConTeXtLMTX/tex/setuptex; >> context {filePath} >> MKIV: >> source /Users/graph/ConTeXt/tex/setuptex; >> context {filePath} >> >> I may avoid it by adding “mtxrun —generate” before compiling it. >> But it isn’t a good solution. >> I think that there is a better way to do this. >> Would you please tell me how to fix it or what is a better way? > Does > > <path to>/mtxrun --autogenerate --script context --autopdf {filePath} > > work in your editor? > > Hans > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- > > > ------------------------------ > > Message: 3 > Date: Fri, 5 Apr 2019 00:37:27 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl>, Dmitry > Starostin <starostin.dmitry(a)gmail.com> > Subject: Re: [NTG-context] (no subject) > Message-ID: <2a626d5a-4378-e1f9-2278-d1496f62f810(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 4/4/2019 9:30 PM, Dmitry Starostin wrote: >> In terminal: >> >> mtxrun --autogenerate --script context --autopdf Test.tex >> >> -> >> >> resolvers | initialization | fatal error: kpse library is accessed >> (key: default_texmfcnf) > this normally means that there is no file database ... context mkiv nor > lmtx doesn't use kpse > > Hans > > > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- > > > ------------------------------ > > Message: 4 > Date: Fri, 5 Apr 2019 08:49:00 +0200 > From: Otared Kavian <otared(a)gmail.com> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] follow up > Message-ID: <84D8FE1D-E7F7-418F-B10F-A141DD6D8CEC(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Hi Dalyoung, > > If this can be of any help, here is what I did in order to install LuaMetaTeX on MacOS in order to use it with TeXShop: > > 1) I downloaded from > http://www.pragma-ade.nl/install.htm > the version of the installer for MacOS and installed a folder named context-osx-64 at an appropriate place (actually at /context-osx-64) > > 2) Then I did > sh install.sh > in that folder, and once the download was finished I replaced the directory texmf-local with a symbolic link to my texmf-local directory (which sits somewhere else) > > 3) In the directory > ~/Library/TeXShop/Engines > I created a new file named LuaMetaTeX.engine containing the following three lines: > > #!/bin/bash > > export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin > > /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf "$1" --purgeall > > 4) Then when opening TeXShop, I can choose from the scroll menu which shows up on the top left of each a tex file, the engine LuaMetaTeX (or I can set it as default in the Preferences) in order to typeset with LuaMetaTeX engine. > > 5) When I need to update the installation I just run again > sh install.sh > from within the directory /context-osx-64 > (The symlink to my texmf-local is not destroyed). > > 6) If I need to typeset a file from a command line in Terminal, then I need to say > > export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin > > before typesetting myfile.tex by saying > > /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf myfile.tex > > (Note that the above command should be issued when one is already in the directory containing myfile.tex, beacuse otherwise the corresponding pdf file will be created in the wrong place…). > > Best regards: OK > >> On 5 Apr 2019, at 00:17, Jeong Dal <haksan(a)me.com> wrote: >> >> Dear Hans, >> >> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side. >> But I have a problem to run it. >> >> If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment. >> “I can’t fine a file …../defFonts.tex” even though it is there. >> To resolve it, I run “mtxrun —generate” in MKIV. >> But it invoke the same type error in LMTX. >> Here are the command in Atom editor which I use to run it. >> >> LMTX: >> source /Users/graph/ConTeXtLMTX/tex/setuptex; >> context {filePath} >> MKIV: >> source /Users/graph/ConTeXt/tex/setuptex; >> context {filePath} >> >> I may avoid it by adding “mtxrun —generate” before compiling it. >> But it isn’t a good solution. >> I think that there is a better way to do this. >> Would you please tell me how to fix it or what is a better way? >> >> Thank you for reading. >> >> Best regards, >> >> Dalyoung >> >> >>> >>> Hi, >>> >>> We have worked furiously all day kicking-out extra code, and are pleased >>> to present a lean-and-mean version of luatex with your favorite ConTeXt. >>> Same good taste but only half the calories and a new name: luametatex >>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can >>> now stand on our own. Of course, good-old luatex and MkIV (as well as >>> MkII) will continue to coexist and be maintained. However, now you will >>> be able to run ConTeXt lmtx on your smart thermostat or on your >>> refrigerator for the Internet of Things - the dawn of a new era! >>> >>> Stay tuned, >>> >>> Alan and Hans >> >> ___________________________________________________________________________________ >> If your question is of interest to others as well, please add an entry to the Wiki! >> >> maillist : ntg-context(a)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 >> ___________________________________________________________________________________ > > > > ------------------------------ > > Subject: Digest Footer > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : https://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > > > ------------------------------ > > End of ntg-context Digest, Vol 178, Issue 19 > ********************************************

2 1

ConTeXt does not respect custom TEXMFHOME location
by Johannes Hermann 08 Apr '19

08 Apr '19

Hello mailinglist, I have a problem with ConTeXt (Texlive 2019) and setting a custom location of TEXMFHOME. After installation I end up with a /usr/local/texlive/2019/texmfcnf.lua as follows: return { content = { variables = { TEXMFHOME = "~/.texlive2019/texmf", }, }, } Now when I place my custom version of publ-aut.lua in the appropriate subfolder it is not used. Although this works when default TEXMFHOME is used. Is this behavior known or is this a bug? Johannes

2 1

Is t-vim still available in LMTX?
by seasoul 08 Apr '19

08 Apr '19

Dear List, I just installed LMTX and start to use. I found t-vim is not installed even I use "modules = all”. So is t-vim still supported and could be used as usual? Or there is the plan to develop a core function to pretty printing? -- Yours Sincerely Diego

2 1

Layer failure with LMTX
by Rik Kabel 08 Apr '19

08 Apr '19

List, The following example works as expected with MKIV but fails for me with LMTX. \setuppapersize[A7] \setuppagenumbering [location=] \definelayer [pageNumber][ x=\dimexpr\pagewidth-\cutspace\relax, y=\topspace, width=\pagewidth, height=\pageheight, ] \startsetups [setupPage] \setlayer[pageNumber] {\hskip\leftmargindistance \inframed[frame=off,leftframe=on,loffset=1em]{\userpage}} \stopsetups \setupbackgrounds[page] [setups=setupPage, background=pageNumber] \starttext \page[empty] \stoptext -- Rik

2 1

additional space with sidebar and narrower
by Henning Hraban Ramm 07 Apr '19

07 Apr '19

Ahoi, I’m trying to mark examples in a book with indent (\startnarrower) and a rule in the margin (\startsidebar). Each of those works on its own as it should, but combined there’s an additional empty line before and after introduced that I can’t get rid of. Any hints? \starttext \input tufte \startsidebar \startnarrower \input knuth \stopnarrower \stopsidebar \input tufte \stoptext Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

4 7

\hbox dir TRT syntax error with LMTX
by Joseph Canedo 07 Apr '19

07 Apr '19

Dear all, Trying to compile this MWE \starttext \hbox dir TRT{TRT box} \stoptext Fails with context LMTX command with error : tex error > tex error on line 3 in file c:/Users/Jo/Documents/Bible/Bibles/Olivetan/Tests/test_hbox_dir.tex: ! Missing { inserted <to be read again> d <to be read again> d ir <to be read again> l.3 \hbox dir TRT{TRT box} 1 \starttext 2 3 >> \hbox dir TRT{TRT box} 4 5 \stoptext 6 What’s the syntax for setting box direction now please? Thanks Joseph

2 1

name of cache used by mkiv and lmtx
by Aditya Mahajan 07 Apr '19

07 Apr '19

Hi, I am currently using mkiv and lmtx in parallel and noticed that both use the same texmf-cache subdirectory. Running: mtxrun --script cache --list gives mtx-cache | writable path: /home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mtx-cache | mtx-cache | tma : 59 mtx-cache | tmc : 59 mtx-cache | rest : 35 mtx-cache | total : 153 mtx-cache | on both distributions. A consequence of this is that whenever I switch distributeions the font used in the document gets "compiled" and "dumped", i.e., I get messages: system > lua > compiling '/home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tma' into '/home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tmc' system > lua > dumping '/home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tma' into '/home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tmc' stripped fonts > otf loading > loading '/opt/context-minimals/texmf/fonts/opentype/public/lm/lmroman12-regular.otf', hash 'lmroman12-regular' Is there a way to avoid that? I can, of course, set different values of TEXMFCACHE for both distributions, but does it make sense to to use a different hash (5fe67e...) for the two? Thanks, Aditya

3 4

Undefined symbol lua_gettop
by Aditya Mahajan 06 Apr '19

06 Apr '19

Hi, I am experimenting with using lua libraries with lmtx. I tried the following: 1. Download the lcomplex library (from http://webserver2.tecgraf.puc-rio.br/~lhf/ftp/lua/ar/lcomplex-100.tar.gz) 2. Untar and modify the Makefile so that LUA_TOPDIR points to the right location (/usr in my case). 3. Run make. This creates a complex.so file in the current directory. 4. Create a test file (and put complex.so in the same directory) \starttext \startluacode local complex=require("complex") z = complex.new(1,1); context("The absolute value of $z=%f + j%f$ is $%f$", z:real(), z:imag(), z:abs()); \stopluacode \stoptext This file runs correctly with mkiv, but when I try to run it with lmtx, I get the error lua error > lua error on line 8 in file /home/adityam/Software/lcomplex/lcomplex-100/test.tex: ...etatex/texmf-context/tex/context/base/mkiv/l-package.lua:325: error loading module 'complex' from file './complex.so': ./complex.so: undefined symbol: lua_gettop Any idea why this is happening and what I can do to fix it? Aditya

2 1