Stabilizing and improving conjure.nvim (Conjure support for nvim)

[niklasdewally]

A small project for any vim users that pass by :)

Background
I quickly hacked together a few essence language detection plugins and the Conjure LSP server to create a neovim plugin for writing Conjure models. This detects the essence filetype, provides basic highlighting, and runs the LSP server for us.

https://github.com/niklasdewally/conjure.nvim

It is a bit hacky still, so:

1. It needs documentation hover support.
2. It supports the conjure vscode snippets, but I just manually copied them into the repo - these could be refactored out into their own repo so that multiple language extensions (including this one and Make a conjure extension for intelli J  #12) can use it.
3. Proper docs and testing are not there yet.
4. This plugin amalgamates various random "essence in vim" plugins I found in Github search. Having a properly defined vim "user workflow" in the official documentation would be helpful.
5. Not sure if this is possible, but adding Conjure to nvim-lspconfig and Mason and so on would be good.

As conjure.nvim mainly uses the LSP server and VSCode snippets, it should not require much maintenance in itself - the main challenge is working out how to keep the LSP and snippets up to date across multiple editor plugins.

Related work

#12 suggests a similar extension for IntelliJ.

[niklasdewally]

Even if no-one ends up writing essence in vim apart from me and Kieran, making the snippets part of the VSCode plugin independent of the VSCode plugin is probably a good idea, as most editors can read VSCode snippet files anyways :)