From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: How to write readable source files?
Date: Sat, 29 May 2021 15:03:39 -0000 (UTC) [thread overview]
Message-ID: <s8tl4b$enp$1@ciao.gmane.io> (raw)
In-Reply-To: <ed70e046-edb9-f01b-e04f-2cc3abfbe9b5@xs4all.nl>
On 2021-04-25, Hans Hagen <j.hagen@xs4all.nl> wrote:
>> If there is a way to automatically get a list of all ConTeXt commands
>> and options (and, ideally, MetaFun defs, types, and other keywords), I'd
>> be happy to improve omni-completion for ConTeXt in Vim.
> All is in xml files (i-*.xml) in the distribution maintained by
> Wolfgang. We ship with this for editors:
>
> >dir t:\texmf\context\data
>
> 04/21/2021 11:40 AM <DIR> scite
> 04/21/2021 11:40 AM <DIR> textadept
> 04/21/2021 11:40 AM <DIR> texworks
> 04/21/2021 11:40 AM <DIR> vscode
>
> 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.
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?
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.
I have used a custom script in the past for fine-grained keyword
extraction from MetaFun's source code. By fine-grained, I mean that the
output contains information about the kind of keyword (def, primary def,
vardef, constant, variable, etc.) I could update it to Lua and mp-*.mpxl
if that interests you—unless that has already been done, of course.
Nicola
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-05-29 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 9:45 Jan U. Hasecke
2021-04-24 11:55 ` Henning Hraban Ramm
2021-04-24 13:25 ` Hans van der Meer
2021-04-24 13:45 ` juh
2021-04-24 19:25 ` Nicola
2021-04-25 7:13 ` juh
2021-04-25 12:12 ` Nicola
2021-04-25 12:24 ` Hans Hagen
2021-05-29 15:03 ` Nicola [this message]
2021-05-29 17:08 ` Hans Hagen
2021-05-29 18:29 ` Nicola
2021-05-29 23:04 ` Hans Hagen
2021-05-30 8:13 ` Nicola
2021-04-24 12:12 ` luigi scarso
2021-04-24 15:17 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='s8tl4b$enp$1@ciao.gmane.io' \
--to=nvitacolonna@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).