On 2021-05-29, Hans Hagen
On 5/29/2021 5:03 PM, Nicola wrote:
these lists are generated by mtx-interface so we can add more if needed
Could you please elaborate on the (automatic?) data flow from ConTeXt's source files to data files for each application? Is it:
source code -> XML -> .lua -> mtx-interface -> data?
In particular, it is not clear to me how i-*.xml files are related to mtx-interface, as the latter does not use them directly, AFAICS.
for sure it does
Ok, my cursory look was then… too cursory. I'll dig better.
Anyway, mtx-interface seems exactly what I am looking for, and I would like to use it to generate ConTeXt keywords for Vim. Can I patch that script?
basically we only need
function flushers.vim(collected) end
Ok.
For MetaFun keywords I don't know yet: do those XML files contain enough information about the content of all mp-* source files? E.g., the fact that `hlingrid` is a def? Looking at the Scite files, I see only internals and commands, and they seem to cover only the "main" MetaFun names.
it is still on the agenda to make xml files for metafun but there is no timeline for that
So, is it correct that the XML files are automatically generated from the source code, and kept in sync with it? If so, how is that done? Or are they manually curated? I'd be willing to contribute to make progress on the MetaFun part.
just look at the files in the scite path ... much info is available, for context it comes from the xml files, for the tex engine and meta* it comes from mult* lua files
Ok, I'll look there.
adding more detail (not sure if distinguishing between def and vardef makes sense ... we more use the 'primitive', 'lowlevel', 'interface' kind of grouping
Whatever you think is more appropriate... Provided that it can be parsed automatically. Nicola