On Mon, 9 Aug 2021, Hans Hagen wrote:

> On 8/8/2021 11:53 PM, Aditya Mahajan via ntg-context wrote:
> > On Sun, 8 Aug 2021, Hans Hagen via ntg-context wrote:
> > 
> > > On 8/8/2021 1:13 PM, Benjamin Buchmuller via ntg-context wrote:
> > > > I'm not sure if it's related to this latest:
> > > > 
> > > > ConTeXt  ver: 2021.08.07 22:53 LMTX  fmt: 2021.8.8  int: english/english
> > > > 
> > > > or a previous one, but with this one:
> > > > 
> > > > ConTeXt  ver: 2021.07.30 00:57 LMTX  fmt: 2021.8.8  int: english/english
> > > > 
> > > > My document compiled fine.
> > > > 
> > > > When I use the t-vim module (freshly installed again from the garden;
> > > > but I
> > > also tried to replace some files from the GitHub, but not sure if I did it
> > > right …), I now get an error when I do something like
> > > > 
> > > > \usemodule[vim]
> > > > 
> > > > \definevimtyping[vimR]
> > > > 
> > > > \typevimRfile{path_to_file.R} % specifically: {../sourcecodes/myfile.R}
> > > > 
> > > > --
> > > > 
> > > > lua error > lua error on line 2 in file virtual://block.sourcecode.7:
> > > > 
> > > > token call, execute:
> > > ...ConTeXt/tex/texmf-context/tex/context/base/mkiv/l-io.lua:70: bad
> > > argument
> > > #1 to '?' (string expected, got nil)
> > > i'll check it, i cleaned up some code but didn't realize that it was
> > > used in a module
> > 
> > This was also reported on t-vim's github page:
> > https://github.com/adityam/filter/pull/48.
> > 
> > I basically use jobs.file.run to cache the results and I can easily write a
> > module specific version of that, if needed. I'll look at it in a day or two
> > (away from a stable internet connection until then).
> blame me for this one
> 
> just wait for the update (i added the name,action interface again as i assumes
> the { filename =, action= } usage)

For the record, the vim module is working again with version 2021.08.10. Thanks Hans!

Aditya