Usage
zonvie [OPTIONS] [--] [NVIM_ARGS...]Command-line options
Section titled “Command-line options”| Option | Description |
|---|---|
--nofork |
Don’t fork; stay attached to terminal, keep cwd |
--nvim <path> |
Path to Neovim executable (overrides config) |
--log <path> |
Write application logs to the specified file path |
--extcmdline |
Enable external command line UI |
--extpopup |
Enable external popup menu UI |
--extmessages |
Enable external messages UI |
--exttabline |
Enable external tabline UI |
--extwindows |
Enable external windows (each Neovim window as an OS window) |
--ssh=<user@host[:port]> |
Connect to a remote host via SSH |
--ssh-identity=<path> |
Path to SSH private key file |
--devcontainer=<workspace> |
Run inside a devcontainer |
--devcontainer-config=<path> |
Path to devcontainer.json |
--devcontainer-rebuild |
Rebuild devcontainer before starting |
--connect-nvim=<addr> |
Attach to a running Neovim server. Address — POSIX: TCP host:port or Unix socket path; Windows: named pipe path (e.g. \\.\pipe\nvim.31920.0). Mutually exclusive with --ssh / --devcontainer / --wsl. |
--remote-ui=<addr> |
Alias of --connect-nvim, mirrors nvim --remote-ui |
--install |
Create the default config file and exit |
-- |
Pass all remaining arguments to nvim |
--help, -h |
Show help message |
Examples
Section titled “Examples”# Open a filezonvie file.txt
# Use a custom nvim configzonvie -- -u ~/.config/nvim/minimal.lua
# Connect to a remote host via SSHzonvie --ssh=user@example.com
# Run in a devcontainerzonvie --devcontainer=/path/to/project
# Attach to a Neovim server already running (e.g. started elsewhere with# `nvim --headless --listen /tmp/nvim.sock` or `:detach`'d from another UI)zonvie --connect-nvim=/tmp/nvim.sock # POSIX: Unix socketzonvie --connect-nvim=127.0.0.1:6789 # POSIX: TCPzonvie --connect-nvim=\\.\pipe\nvim.31920.0 # Windows: named pipe