Re: [NTG-context] t-vim module: no highlighting for custom filetypes

On 5/21/2021 9:37 PM, Nicola wrote:

On 2021-05-21, Aditya Mahajan wrote:

...

nvim was 8-10% faster than vim in my tests:

https://adityam.github.io/context-blog/post/vim-vs-neovim/

Interesting, thanks for sharing.

...

I actually want t-vim (or rather t-filter) to support more editors/syntax highlighters. At some stage I had added rudimentary support for other syntax highlighters most of them required scaffolding to wrap around the latex output:

https://adityam.github.io/context-blog/post/clean-tex-output/

I think I have said that already, but it is worth repeating: t-vim is a genius idea! Vim is universally available and it supports almost any imaginable syntax. t-vim makes creating code-oriented documents absolutely painless (ConTeXt helps, of course). And it makes me scream when I have to do that in LaTeX. So, kudos for that. Personally, I do not think that supporting other highlighters would add much value to what is already there. But if it is possible to make the module more general without overcomplicating it, it might be a good idea.

I have only a minor annoyance: I have just noticed that -- is typeset as an en-dash in LMTX (but not in MKIV, as documented). Could you look into that?

best is that the module uses: \the\everyinitializeverbatim because there we disable all kind of non verbatim stuff Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------