Re: [dev-context] setup-en.pdf and mkiv command list

Hans Hagen 15. Mai 2017 um 21:45 On 5/15/2017 9:00 PM, Wolfgang Schuster wrote: i assume that with primitive you mean primitive context No, TeX primitives. Wolfgang ___ dev-context mailing list dev-context@ntg.nl

Re: [dev-context] setup-en.pdf and mkiv command list

On 5/15/2017 9:00 PM, Wolfgang Schuster wrote: is there a need to separate them? after all, most users will not use low level code and when they do it doesn't matter much to them if they're more or less low level low level is fuzzy anyway: \xmlfirst (more low level?) vs \xmlfilter (more

Re: [dev-context] setup-en.pdf and mkiv command list

the command reference is quite complete (and user defined instances will never be part of syntax highlight anyway) OTOH user-defined commands can be added to the ConTeXt lexer via the Style Configurator (Notepad++) and get their own highlight color. I have found this very useful in writing

Re: [dev-context] setup-en.pdf and mkiv command list

On Sun, 14 May 2017 11:38:19 -0600, Wolfgang Schuster wrote: The lua tables in the scite distribution are incomplete. For example, in scite-context-data-interfaces.lua there is no mention of the commands for natural tables - \bTABLE etc. This is the reason for

Re: [dev-context] setup-en.pdf and mkiv command list

On Sun, 14 May 2017 09:33:04 -0600, Hans Hagen wrote: 1. Clarification: Does setup-en.pdf includes both mkii and mkiv commands? If so, then can a version of the auto-generation script be made that will generate a version setup-mkiv-en.pdf that is complete but restricted to mkiv

Re: [dev-context] setup-en.pdf and mkiv command list

On Sun, 14 May 2017 09:33:04 -0600, Hans Hagen wrote: 2. Modification: It appears that all command names that appear in slanted text are used to mention user-defined commands of a particular class, e.g., /\BACKGROUND/ - slanted text which obviously names each of a class of