From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: Nicola via ntg-context <ntg-context@ntg.nl>
Cc: Alan Braslau <alan.braslau@icloud.com>, Nicola <nvitacolonna@gmail.com>
Subject: Re: (any) neovim users?
Date: Fri, 14 Oct 2022 11:26:59 -0600 [thread overview]
Message-ID: <20221014112659.5d53edfb@boo.my.domain> (raw)
In-Reply-To: <tic3ta$vga$1@ciao.gmane.io>
On Fri, 14 Oct 2022 16:48:42 -0000 (UTC)
Nicola via ntg-context <ntg-context@ntg.nl> wrote:
> On 2022-10-14, Alan Braslau via ntg-context <ntg-context@ntg.nl>
> wrote:
> > A recent upgrade of the editor neovim leads to the following error
> > when using %&context identification at the head of .tex source
> > files.
>
> The ConTeXt plugin (as well as MetaPost and MetaFont ones) has
> recently been rewritten in Vim 9 script (the new scripting language
> embedded in Vim), which NeoVim does not support, afaik. See this
> thread: https://github.com/vim/vim/issues/10968.
>
> One thing you can do is: grab the old runtime files and put them in
> you own ~/.vim directory (following a similar layout). You may get
> those from the `runtime` folder of the Vim project:
> https://github.com/vim/vim, or from NeoVim repo. Just checkout
> a revision with the old scripts (searching for "update runtime" in the
> commit logs should help you filter the relevant commits).
>
> Nicola
Thank you,
I wonder why a lua error is reported?
I also worry that %@context support has now diverged (for whatever reason) and that Context highlighting is now limited to the one "vim" variant of the vi editor. Using old runtime files in one's personal .vim directory locks one into unmaintained (by the Context community) syntax. I wish that a better solution were available.
Beyond this, I would think that neovim with lua scripting would be greatly preferable to vim9scripting. Indeed, while I do not know anything about the details, perhaps it could even use the same lpeg code as developed for the Scite editor.
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-10-14 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 15:00 Alan Braslau via ntg-context
2022-10-14 16:48 ` Nicola via ntg-context
2022-10-14 17:26 ` Alan Braslau via ntg-context [this message]
2022-10-14 18:59 ` Nicola via ntg-context
2022-10-14 20:21 ` Henning Hraban Ramm via ntg-context
2022-10-14 22:05 ` Alan Braslau via ntg-context
2022-10-14 22:16 ` Alan Braslau via ntg-context
2022-10-15 7:45 ` Hans Hagen via ntg-context
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=20221014112659.5d53edfb@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@icloud.com \
--cc=nvitacolonna@gmail.com \
/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).