Hi,

I had two issues with luametatex:

The manual documents getters and setters for the directions:

The direction states can be queried and set with:
tex.gettextdir() tex.getpardir()          tex.setmathdir(<number>)
tex.getlinedir() tex.settextdir(<number>) tex.setpardir(<number>)
tex.getmathdir() tex.setlinedir(<number>) 

While there is no problem with the set...dir commands, the get...dir
commands don't actually exists. (They can be implemented using tex.get,
but it would be nice if either they were added to luametatex or if they
were removed from te documentation to avoid confusion.)

Additionally the scanning variant of \Umathcodenum seems broken:

Take the example document

\starttext
\directlua{
  print('gettextdir:', tex.gettextdir)
}
\the\Umathcodenum`a
\stoptext

It works in ConTeXt mkiv, but in lmtx it shown a (non-informative) error:

  gettextdir:   nil

  tex error       > tex error on line 5 in file ./contfail.tex: ! This can't 
happen (scan char)

  l.5 \the\Umathcodenum`a
                       

  1     \starttext
  2     \directlua{
  3       print('gettextdir:', tex.gettextdir)
  4     }
  5 >>  \the\Umathcodenum`a
  6     \stoptext
  7     


  I'm broken. Please show this to someone who can fix me.


  mtx-context     | fatal error: return code: 256

(\Umathcodenum`a=123 seems to work though)

Also especially these "This can't happen" errors a a it of pain debug
without having the option to look into the source which I can't find
anywhere. Has that been released? Is it still planned to make it
available at some point?


Best regards,
Marcel Krüger
___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to