4 releases

Uses new Rust 2021

0.1.3 Jul 17, 2022
0.1.2 Jul 16, 2022
0.1.1 Jul 16, 2022
0.1.0 Jul 16, 2022

#13 in Text editors

Download history 24/week @ 2022-07-10 103/week @ 2022-07-17 69/week @ 2022-07-24 130/week @ 2022-07-31 7/week @ 2022-08-07

333 downloads per month

MIT license


🔗 nvim-oxi

Latest version Docs MSRV CI


The nvim-oxi crate provides first-class Rust bindings to the rich API exposed by the Neovim terminal text editor.

The project is mostly intended for plugin authors, although nothing's stopping end users from writing their Neovim configs in Rust.


The traditional way to write Neovim plugins in languages other than the "builtin" ones, i.e. Vimscript or Lua, is via RPC channels. This approach comes with a few limitations mostly due to having to (de)serialize everything to MessagePack-encoded messages, prohibiting things like attaching callbacks to keymaps or scheduling functions.

nvim-oxi takes a different approach. It leverages Rust's foreign function interface (FFI) support to hook straight into the Neovim C code, allowing feature parity with "in process" plugins while also avoiding the need for an extra IO layer.

This thread on the Neovim discourse goes into a bit more detail for anyone who's interested.


Why bother when Neovim already has Lua as a first-class citizen? Mainly two reasons:

  • access to the Rust ecosystem: Lua is a great, minimal scripting language but can also be limiting when writing more complex plugins. In contrast Rust is a fully-fledged, statically typed language with a huge ecosystem of crates for (de)serialization, networking, IO, green threads, etc;

  • nvim-oxi provides a fully typed API: everything from optional function fields to callback arguments is checked at compile-time. This allows plugin authors to spend less time reading through the help docs and more time iterating via cargo checks.


The examples directory contains several examples of how to use nvim-oxi. It also contains instructions on how to setup your Rust crate, where to place the compiled artifacts and how to load the final plugin from Neovim.

If you're still not sure about something feel free to open a new issue and I might add a new example documenting your use case (if it can be done).


The test feature flag enables the #[nvim_oxi::test] proc macro. This macro replaces the regular #[test] annotations and can be used to test a piece of code from within a Neovim instance using Rust's excellent testing framework.

For example:

use nvim_oxi::{self as oxi, api};

fn set_get_del_var() {
    api::set_var("foo", 42).unwrap();
    assert_eq!(Ok(42), api::get_var("foo"));
    assert_eq!(Ok(()), api::del_var("foo"));

Then cargo test will spawn a new Neovim process with an empty config, run that code and exit. There are a couple of gotchas:

  • after changing a piece of code, cargo build has to be run before you can test that with cargo test;

  • you cannot have two test functions with the same name, even if they belong to different modules. For example this won't work:

mod a {
    fn foo() {}

mod b {
    fn foo() {}


~31K SLoC