ntg-context May 2022

ntg-context@ntg.nl

57 participants
105 discussions

fatal error again in LMTX
by Pablo Rodriguez 02 May '22

02 May '22

Hi Hans, as already reported (https://mailman.ntg.nl/pipermail/ntg-context/2022/105443.html), LMTX (from 2022.05.02 16:19) quits messaging only fatal error with such a sample: \starttext \startitemize \item one \stoptext I know that \stopitemize is missing above. But in real--world documents, this mistake may need hours to be fixed. Would it be possible that LMTX could provide more verbose information about unfinished \start-commands? Many thanks for your help, Pablo

1 0

process list items differently depending on position in list
by denis.maier＠unibe.ch 02 May '22

02 May '22

Hi, I need to process a comma separated list, and adapt the formatting according to the position of an item in the list (example below). Expected output would be: {\bf foo }, {\em bar} and baz. Is that possible? Can I somehow get the position of an item in the list? (My understanding is that \processcommalist and \processcommacommand apply a command to each list item, but there is no such thing as <position in the list>... I hope I'm wrong here.) Or is that something where using Lua would be a better choice? Best, Denis %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \define[1]\command {#1} \define\somelist {foo, bar, baz} \starttext \processcommacommand [\somelist] \command \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

2 3

\getcommacommandsize not working in lmtx
by denis.maier＠unibe.ch 02 May '22

02 May '22

Hi, I've just ran into a behaviour that runs against what is shown on the wiki, https://wiki.contextgarden.net/System_Macros/Comma_Separated_Lists Maybe a bug? The wiki says you can use \getcommacommandsize to get the length of a comma separated list, but it does not seem to work. MWE below. Best, Denis \define\somelist {foo, bar, baz} \starttext \getcommacommandsize[\somelist] \commalistsize % Expected : 3 % Actual : 1 \expandafter\getcommalistsize\expandafter[\somelist] \commalistsize % Expected : 3 % Actual : 3 \stoptext

2 1

recursion in a table
by Henning Hraban Ramm 02 May '22

02 May '22

Hi, I was playing with the example from https://wiki.contextgarden.net/Scaling_Rotating_Mirroring_Clipping#Location… and tried to put it in a tabulate: \useMPlibrary[dum] \setupexternalfigures[width=3em,height=2em,frame=on,] %\def\TXT{\ruledhbox{\bf(XyX)}} \def\TXT{\externalfigure[pic]} \starttabulate[|l|l|l|l|l|l|] \NC\NC normal\NC depth\NC fit\NC broad\NC high\NC\NR \HL \dostepwiserecurse{0}{359}{45}{% %\expanded{\setuprotate[rotation=\recurselevel]} \NC{\expanded{\recurselevel}˚}% \NC{\ruledhbox{X\rotate[location=normal,rotation=\recurselevel]{\TXT}X}}% \NC{\ruledhbox{X\rotate[location=depth,rotation=\recurselevel] {\TXT}X}}% \NC{\ruledhbox{X\rotate[location=fit,rotation=\recurselevel] {\TXT}X}}% \NC{\ruledhbox{X\rotate[location=broad,rotation=\recurselevel] {\TXT}X}}% \NC{\ruledhbox{X\rotate[location=high,rotation=\recurselevel] {\TXT}X}}% \NC\NR} % \HL % error \stoptabulate This works, but \recurselevel is always 0. I know I must expand it (like in the original example), but I can’t make it work within the tabulation. In the first column, \expanded{\recurselevel} stays 0, and rotation=\expanded{\recurselevel} gives an error, while the \setuprotate line has no effect (if I remove "rotation=\recurselevel", of course). How would that work? Also, \HL doesn’t work at the end, and the second line of the error message makes no sense: """ I expect to see \noalign only after the \cr of an alignment. Proceed, and I'll ignore this case. mtx-context | fatal error: return code: 1 """ Hraban

3 2

Fuzzy paragraph when exporting to XML
by Aditya Mahajan 01 May '22

01 May '22

Hi, I am trying to debug a bug-report for t-vim: https://github.com/adityam/filter/issues/64 Exporting with trackers=export* gives a warning: backend > export > fuzzy paragraph: I have managed to narrow it down to the attached MWE (which does not depend on the t-vim module at all). Compiling it using $context --trackers=export\* lines gives the fuzzy paragraph warning. Any hints on how to resolve this? Thanks, Aditya

2 3

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context May 2022