Neovide supports a few command line arguments for effecting things which couldn't be set using normal vim variables.
$ in front of a word refers to it being an "environment variable" which is checked for, some
settings only require it to be set in some way, some settings also use the contents.
--version or -V
Prints the current version of neovide.
--help or -h
Prints details about neovide. This will be a help page eventually.
--frame or $NEOVIDE_FRAME
Can be set to:
full: The default, all decorations.
none: No decorations at all. NOTE: Window cannot be moved nor resized after this.
- (macOS only)
transparent: Transparent decorations including a transparent bar.
- (macOS only)
buttonless: All decorations, but without quit, minimize or fullscreen buttons.
Sets the initial neovide window size in characters.
Enables the log file for debugging purposes. This will write a file next to the executable containing trace events which may help debug an issue.
Maximize the window on startup, while still having decorations and the status bar of your OS visible.
This is not the same as
g:neovide_fullscreen, which runs Neovide in "exclusive fullscreen",
covering up the entire screen.
--multigrid or $NEOVIDE_MULTIGRID
This enables neovim's multigrid functionality which will also enable floating window blurred backgrounds and window animations. For now this is disabled due to some mouse input bugs upstream (neovim/neovim/pull/12667, neovim/neovim/issues/15075) and some floating window transparency issues.
By default, neovide detaches itself from the terminal. Instead of spawning a child process and leaking it, be "blocking" and have the shell directly as parent process.
Instead of skipping some frames in order to match
g:neovide_refresh_rate, render every possible
Don't request sRGB on the window. Swapping sometimes fixes startup issues.
By default, Neovide opens files given directly to Neovide (not NeoVim through
--!) in multiple
tabs to avoid confusing new users. The option disables that and makes multiple given files to normal
Note: Even if files are opened in tabs, they're buffers anyways. It's just about them being visible or not.
What IP and port to use when connecting to neovim.
Runs neovim from inside wsl rather than as a normal executable.
Sets where to find neovim's executable. If unset, neovide will try to find
nvim on the
environment variable instead. If you're running a Unix-alike, be sure that binary has the executable
permission bit set.
--wayland-app-id <wayland_app_id> or $NEOVIDE_APP_ID --x11-wm-class-instance <x11_wm_class_instance> or $NEOVIDE_WM_CLASS_INSTANCE --x11-wm-class <x11_wm_class> or $NEOVIDE_WM_CLASS
On Linux/Unix, this alters the identification of the window to either X11 or the more modern Wayland, depending on what you are running on.