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

Hans Hagen mailto:pragma@wxs.nl 15. Mai 2017 um 11:43 On 5/14/2017 8:55 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

...

On Sun, 14 May 2017 12:20:43 -0600, Wolfgang Schuster wrote:

...

...

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 long documents. See attached (User-defined Keywords dialog).

You can limit the number of custom commands when you use

\startnamedsection[topic][title=...]

instead of

\starttopic[title=...]

First time encountering these two commands; they're not on the wiki, need to learn more about them..

in mkiv most commands that have generated names also provide generic instance handling, like here

...

Can you explain or give a complete sample test file illustrating how they apply in the matter under discussion? Thanks.

afaiks there is not much to add to the above example unless i misunderstood; basically one can always use "topic" as instance name to do something instead of \somecommandwith<topic>init

...

something like the following:

TeX primitives - Knuth luaTeX primitives - excluding Knuth macro structure - e.g., sectioning etc. micro structure - e.g., itemizations, tables etc.

here i have document level (\startdocument etc) vs the rest

...

mode structure - e.g., metapost, xml, markdown MkiV - remaining high level MkIV - low-level [but how to separate them out?]

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 generic) I can add class="system|primitive" (or level="...") to the XML files, commands without attribute are user-level.

Wolfgang