From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: new upload/issue with t-vim?
Date: Fri, 13 Aug 2021 23:46:43 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2108132326450.1167473@nqv-guvaxcnq> (raw)
In-Reply-To: <977d017a-f9a1-187a-f203-9171558945e7@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
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
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-08-14 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1628416801.4772.ntg-context@ntg.nl>
2021-08-08 11:13 ` Benjamin Buchmuller via ntg-context
2021-08-08 12:31 ` Hans Hagen via ntg-context
2021-08-08 21:53 ` Aditya Mahajan via ntg-context
2021-08-08 23:16 ` Hans Hagen via ntg-context
2021-08-14 3:46 ` Aditya Mahajan via ntg-context [this message]
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=nycvar.YAK.7.78.908.2108132326450.1167473@nqv-guvaxcnq \
--to=ntg-context@ntg.nl \
--cc=adityam@umich.edu \
/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).