Skip to main content

Control Neovim instances using "nvr" commandline tool

Project description

Logo

Intro

nvr is a tool that helps controlling nvim processes.

It basically does two things:

  1. adds back the --remote family of options (see man vim)

  2. helps controlling the current nvim from within :terminal

To target a certain nvim process, you either use the --servername option or set the environment variable $NVIM_LISTEN_ADDRESS.

Since $NVIM_LISTEN_ADDRESS is implicitely set by each nvim process, you can call nvr from within Neovim (:terminal) without specifying --servername.

Installation

$ pip3 install neovim-remote

On most systems this will be good enough.

If you get a “permission denied” error, don’t use sudo to force it! Use this instead:

$ pip3 install --user neovim-remote

..and make sure that ~/.local/bin is in $PATH.

Usage

Start a nvim process (which acts as a server) in one shell:

$ NVIM_LISTEN_ADDRESS=/tmp/nvimsocket nvim

And do this in another shell:

$ # Spares us from using --servername all the time:
$ export NVIM_LISTEN_ADDRESS=/tmp/nvimsocket
$ # This is optional, since nvr assumes /tmp/nvimsocket by default.

$ # Open two files:
$ nvr --remote file1 file2

$ # Send keys to the current buffer:
$ nvr --remote-send 'iabc<esc>'
$ # Enter insert mode, insert 'abc', and go back to normal mode again.

$ # Evaluate any VimL expression, e.g. get all listed buffers:
$ nvr --remote-expr "join(sort(map(filter(range(bufnr('$')), 'buflisted(v:val)'), 'bufname(v:val)')), "\""\n"\"")"
.config/git/config
vim/vimrc
zsh/.zprofile

See nvr -h for all options.

FAQ

How to open directories?

:e /tmp opens a directory view via netrw. Netrw works by hooking into certain events, BufEnter in this case (see :au FileExplorer for all of them).

Unfortunately Neovim’s API doesn’t trigger any autocmds on its own, so simply nvr /tmp won’t work. Meanwhile you can work around it like this:

$ nvr /tmp -c 'doautocmd BufEnter'

Reading from stdin?

Yes! E.g. echo "foo\nbar" | nvr -o - and cat file | nvr --remote - work just as you would expect them to work.

Exit code?

If you use a recent enough Neovim, nvr will use the same exit code as the linked nvim.

E.g. nvr --remote-wait <file> and then :cquit in the linked nvim will make nvr return with 1.

Talking to nvr from Neovim?

Imagine nvr --remote-wait file. The buffer that represents “file” in Neovim now has a local variable b:nvr. It’s a list of channels for each connected nvr process.

If we wanted to create a command that disconnects all nvr processes with exit code 1:

command! Cquit
    \  if exists('b:nvr')
    \|   for chanid in b:nvr
    \|     silent! call rpcnotify(chanid, 'Exit', 1)
    \|   endfor
    \| endif

Demos

(Click on the GIFs to watch them full-size.)

Using nvr from another shell: Demo 1

Using nvr from within :terminal: Demo 2

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

neovim-remote-1.5.1.tar.gz (7.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

neovim_remote-1.5.1-py3-none-any.whl (9.7 kB view details)

Uploaded Python 3

File details

Details for the file neovim-remote-1.5.1.tar.gz.

File metadata

  • Download URL: neovim-remote-1.5.1.tar.gz
  • Upload date:
  • Size: 7.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for neovim-remote-1.5.1.tar.gz
Algorithm Hash digest
SHA256 90bce229f6f81e63a647b67a1dbaf08a3bd9fde0564f01f2e4f6172004f6c94c
MD5 4e01f7f703304e04c282532ec925de49
BLAKE2b-256 80fa7d32bdbca9d7849119db53d5661599705a9e2776a23a5e94dc08d794615d

See more details on using hashes here.

File details

Details for the file neovim_remote-1.5.1-py3-none-any.whl.

File metadata

File hashes

Hashes for neovim_remote-1.5.1-py3-none-any.whl
Algorithm Hash digest
SHA256 b6d582eb3da9eb06a3aeaf81450b5c6651c90d4bfdfbbaf6cb1abe61914cd1f2
MD5 03413dcaf1513a0b52500cafcf007fac
BLAKE2b-256 ebf631ac0b45134ebe1b66497bc76894bf715f21f8e70a02a6d4ba39eeb12f26

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page