- ntg-context - NTG Mailing Lists

Parse oddity with modes, compilation halts
by Rik Kabel 02 Jan '18

02 Jan '18

Consider the following example: When this is run with --mode=vim, all is well. When the mode is not set, compilation fails. I suspect that the parser is scanning for the closing curlie of \inlineTEX but never sees it. \starttext \startmode[vim] \usemodule[t-vim] \definevimtyping[TEX][syntax=context] \inlineTEX{%} \stopmode ‽ \stoptext Is there any work-around to prevent this, other than avoiding it completely? -- Rik

2 1

registers with section and line number references
by Pablo Rodriguez 02 Jan '18

02 Jan '18

Dear list, Happy New Year to all list members. I have the following sample: \starttext \startlinenumbering \chapter{One} \index{Zapf}\input zapf \section{Two} \index{Knuth}\input knuth \subsection{Three} \index{Tufte}\input tufte \stoplinenumbering \blank[big] \placeregister[index] \stoptext Which is the way to have sectioning and line number references instead of page references? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

setting row height?
by Floris van Manen 29 Dec '17

29 Dec '17

What is the (preferred) way to set the height of table rows? e.g. the online documentation tells me how to set the width, not the height. or how to set the height of the table? \starttable[*{4}{|w(7mm)}|][textwidth=max]\HL[5] \VL[5]{1} \VL[1]{0} \VL[5]{2} \VL[1]{8} \VL[5]\AR\HL[1] \VL[5]{8} \VL[1]{~} \VL[5]{~} \VL[1]{1} \VL[5]\AR\HL[5] \VL[5]{0} \VL[1]{~} \VL[5]{~} \VL[1]{2} \VL[5]\AR\HL[1] \VL[5]{2} \VL[1]{8} \VL[5]{1} \VL[1]{0} \VL[5]\AR\HL[5] \stoptable Thanks .F

2 2

Can MetaPost draw directly datapoints from a data file?
by Jorge Manuel 28 Dec '17

28 Dec '17

When I need to draw datapoints from a external data file I’m using lua, like this: \starttext \startluacode Elemento = {} x = {} y ={} z= {} carga = {} i=1 context("\\startMPcode”) context("numeric u; u := 1.5cm;") for line in io.lines("molecule.xyz") do local a, b, c, d, e = string.match(line, '(%a+)%s*%s*(%S+)%s*%s*(%S+)%s*%s*(%S+)%s*%s*(%S+)') Elemento[i]= a x[i]= tonumber(b) y[i]= tonumber(c) z[i]= tonumber(d) carga[i]= tonumber(e) context("label(\"%s\", (%0.6f u, %0.6f u));", a, x[i],y[i]) i=i+1 end context("\\stopMPcode”) \stopluacode \stoptext Is there a way to pass directly the external data to MetaPost without using Lua? I know that I can use a similar function to gdata from graph.mp. I try to reuse this piece of code, but not works. \startMPcode vardef Grdln_@#(expr f) = save n_, s_; string s_; s_ = readfrom f; string @#[]; if s_<>EOF: @#1 := loptok s_; n_ = if @#1="%": 0 else: 1 fi; forever: @#[incr n_] := loptok s_; exitif @#[n_]=" "; endfor @#1<>" " else: false fi enddef; Grdln_$("molecule.xyz"); \stopMPcode Jorge

2 2

Re: [NTG-context] type and typing comments for TeX and Lua
by Christoph Reller 28 Dec '17

28 Dec '17

On Wed, 27 Dec 2017 19:53:58 +0100, Pablo Rodriguez <oinos(a)gmx.es> wrote: > could you enable issues in your Bitbucket repository? Issues are enabled now. Cheers, Christoph

1 0

\vec{} arrow length?
by Alan Braslau 27 Dec '17

27 Dec '17

Why is the \vec{} arrow too short in some cases? Compare $\vec{X}$ to $\vec{Y}$. The MWE below looks wrong in the default font and is even uglier when pagella is used. Alan %\setupbodyfont [pagella] \starttext $\vec{X}$ vs. $\vec{Y}$ \stoptext

3 3

type and typing comments for TeX and Lua
by Pablo Rodriguez 27 Dec '17

27 Dec '17

Hans, sorry for insisting, but I really need this. I have the following sample: \definetype[context][option=tex] \definetype[lua][option=lua] \starttext \startTEXpage[offset=2em] a \TEX\ inline comment: \context{ag%befe} \Lua\ inline comment: \lua{agb --efe} \startTEX This is text. % a comment, not \comment \stopTEX \startXML This is text. \stopXML \startLUA if code=="code" then --this is a comment \stopLUA \stopTEXpage \stoptext Would it be possible that all comments in type and typing (at least, for Lua, XML and TeX) would have the same formatting for the whole comment contents, including the comment signs? Sorry, but with the current output, it is hard to see (for total newbies) what is part of the comment and what not. And the text editor will display something different. I’m afraid that the scite module isn’t an option for me. Many thanks for your help, Pablo -- http://www.ousia.tk

3 13

Re: [NTG-context] type and typing comments for TeX and Lua
by Christoph Reller 27 Dec '17

27 Dec '17

On Thu, 21 Dec 2017 21:16:45 +0100, Pablo Rodriguez <oinos(a)gmx.es> wrote: > On 12/21/2017 05:04 PM, Christoph Reller wrote: >> Dear Pablo, >> >> At least for XML you could use my module highlight-xml: >> >> \usemodule[highlight-xml] >> \definetype[xml][option=xml] >> [...] >> Note that even partial XML is highlighted correctly. > > It is really a pity that it lacks TeX, since I’m focused on ConTeXt yet > (after all, it would be a Spanish introduction to ConTeXt ;-)). XML will > come later. Maybe, if I find the time, I will add TeX and Lua to my module some time. > I’m afraid that XML comments are colored the same way with your module > and with standard ConTeXt. That should not be the case. Could it be, that the highlight-xml module fails to load? Please check your log file for a "module not found" entry. I have attached the result of my earlier sample. My module does not come in standard context. You have to download it from https://bitbucket.org/philexander/context-highlight. If general interest is high enough I can ask <whoever is responsible for this> to add it. Kind regards, Christoph

2 2

Re: [NTG-context] type and typing comments for TeX and Lua
by Christoph Reller 27 Dec '17

27 Dec '17

On Tue, Mon, 18 Dec 2017 23:50:09 +0100, Pablo Rodriguez <oinos(a)gmx.es> wrote: > I have the following sample: > > \definetype[context][option=tex] > \definetype[lua][option=lua] > \starttext > \startTEXpage[offset=2em] > > a \TEX\ inline comment: \context{ag%befe} > > \Lua\ inline comment: \lua{agb --efe} > > \startTEX > This is text. % a comment, not \comment > \stopTEX > > \startXML > This is text. > \stopXML > > \startLUA > if code=="code" then --this is a comment > \stopLUA > \stopTEXpage > \stoptext > > Would it be possible that all comments in type and typing (at least, for > Lua, XML and TeX) would have the same formatting for the whole comment > contents, including the comment signs? Dear Pablo, At least for XML you could use my module highlight-xml: \usemodule[highlight-xml] \definetype[xml][option=xml] \starttext \startTEXpage[offset=2em] \xml{attr="value"}\crlf \xml{This is text.} \startXML This is text. \stopXML \stopTEXpage \stoptext Note that even partial XML is highlighted correctly. Cheers, Christoph

3 3

CSV parser fails when header is disabled
by Wolfgang Schuster 27 Dec '17

27 Dec '17

Hi, the rfc4180splitter function from util-prs.lua returns a empty table when the option to turn the first line into a header is disabled. The following example from the source %%%% begin example \starttext \startluacode local mycsvsplitter = utilities.parsers.rfc4180splitter() local crap = [[ "first","second","third","fourth" "1","2","3","4" "a","b","c","d" "foo","bar""baz","boogie","xyzzy" ]] local list, names = mycsvsplitter(crap,true) inspect(list) inspect(names) local list, names = mycsvsplitter(crap) inspect(list) inspect(names) \stopluacode \stoptext %%%% end example returns these tables: %%%% begin result table={ { "1", "2", "3", "4" }, { "a", "b", "c", "d" }, { "foo", "bar\"baz", "boogie", "xyzzy" }, } table={ "first", "second", "third", "fourth", } table={ } nil %%%% end result Wolfgang

3 5