Home Explore Blog CI



neovim

2nd chunk of `runtime/doc/starting.txt`
70ca72a47cb4fd4143409de83da5b3390fa58dab7b5d05e80000000100000fa2

-?
-h		Give usage (help) message and exit.

--version						*-v* *--version*
-v		Print version information and exit.  Same output as for
		|:version| command.

							*--clean*
--clean		Mimics a fresh install of Nvim:
		- Skips initializations from files and environment variables.
		- No 'shada' file is read or written.
		- Excludes user directories from 'runtimepath'
		- Loads builtin plugins, unlike "-u NONE -i NONE".

							*--noplugin*
--noplugin	Skip loading plugins.  Resets the 'loadplugins' option.
		Note that the |-u| argument may also disable loading plugins:
			argument	load vimrc files	load plugins ~
			(nothing)		yes		    yes
			-u NONE			no		    no
			-u NORC			no		    yes
			--noplugin		yes		    no

--startuptime {fname}					*--startuptime*
		During startup write timing messages to the file {fname}.
		This can be used to find out where time is spent while loading
		your |config|, plugins and opening the first file.
		When {fname} already exists new messages are appended.

							*-+*
+[num]		The cursor will be positioned on line "num" for the first
		file being edited.  If "num" is missing, the cursor will be
		positioned on the last line.

							*-+/*
+/{pat}		The cursor will be positioned on the first line containing
		"pat" in the first file being edited (see |pattern| for the
		available search patterns).  The search starts at the cursor
		position, which can be the first line or the cursor position
		last used from |shada|. To force a search from the first
		line use "+1 +/pat".

+{command}						*-+c* *-c*
-c {command}	{command} will be executed after the first file has been
		read (and after autocommands and modelines for that file have
		been processed).  "command" is interpreted as an Ex command.
		If the "command" contains spaces, it must be enclosed in
		double quotes (this depends on the shell that is used).
		Example: >
			vim  "+set si"  main.c
			vim  "+find stdio.h"
			vim  -c "set ff=dos"  -c wq  mine.mak
<
		Note: You can use up to 10 "+" or "-c" arguments in a Vim
		command.  They are executed in the order given.  A "-S"
		argument counts as a "-c" argument as well.

--cmd {command}						*--cmd*
		{command} will be executed before processing any vimrc file.
		Otherwise, it acts like -c {command}.  You can use up to 10 of
		these commands, independently from "-c" commands.

							*-S*
-S [file]	Executes Vimscript or Lua (".lua") [file] after the first file
		has been read. See also |:source|. If [file] is not given,
		defaults to "Session.vim". Equivalent to: >
			-c "source {file}"
<		Can be repeated like "-c", subject to the same limit of 10
		"-c" arguments. {file} cannot start with a "-".

-L							*-L* *-r*
-r		Recovery mode.  Without a file name argument, a list of
		existing swap files is given.  With a file name, a swap file
		is read to recover a crashed editing session.  See
		|crash-recovery|.

							*-R*
-R		Readonly mode.  The 'readonly' option will be set for all the
		files being edited.  You can still edit the buffer, but will
		be prevented from accidentally overwriting a file.  If you
		forgot that you are in View mode and did make some changes,
		you can overwrite a file by adding an exclamation mark to
		the Ex command, as in ":w!".  The 'readonly' option can be
		reset with ":set noro" (see the options chapter, |options|).
		Subsequent edits will not be done in readonly mode.
		The 'updatecount' option will be set to 10000, meaning that
		the swap file will not be updated automatically very often.
		See |-M| for disallowing modifications.

							*-m*
-m		Modifications not allowed to be written.  The 'write' option
		will be reset, so that writing files is disabled.  However,
		the 'write' option can be set to enable writing again.

							*-M*
-M		Modifications not allowed.  The 'modifiable' option will be
		reset, so that changes are not allowed.  The 'write' option
		will be reset, so that writing files is disabled.  However,
		the 'modifiable' and 'write' options can be

Title: Nvim Startup Options Continued: Help, Version, Clean, Plugins, and More
Summary
This section continues the explanation of Nvim startup options. It details options for displaying help and version information, starting Nvim in a 'clean' state (mimicking a fresh install), skipping plugins, and measuring startup time. It also covers options for positioning the cursor, executing commands before or after file loading, executing Vimscript files, entering recovery mode, readonly mode, and disallowing modifications.