Skip to content

aconverse/znvr

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ZNVR

A remote control for neovim.

Features

  • Manually select or automatically detect neovim socket address
  • Support for --remote, --remote-tab, --remote-send, --remote-expr from vim/neovim
  • Support for --remote-cd to change the remote directory.
  • Supports Windows, macOS, and Linux

Why ZNVR Instead of Neovim CLI

Neovim CLI has some behaviors that are inflexible and high friction. Neovim CLI will not auto detect a socket address. Neovim CLI will fail out of a lot of scenarios by opening a new interactive neovim instance.

Neovim developers don't seem committed to building quality of life features around the current remote interface (as is their prerogative). neovim/neovim#18414

Why ZNVR Instead of neovim-remote

Znvr builds a single mostly static binary with no runtime needed. Znvr treats windows as a first-class target.

Why Zig

It's got a lot of buzz and I wanted to give it a try. It's got great C interop and is good for building a small, self-contained executable.

Why add Lua

Lua is Neovim's scripting language. Letting Neovim use its own directory and globbing rules, rules results in a consistent file handling experience.

Znvr is still a mostly static zig binary that doesn't link Lua. The Lua code is sent to Neovim for remote execution.

Building from Source

Run zig build, then the executable will be in zig-out/bin/.

About

a remote for neovim

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published