From :h -u
:
-u {vimrc} The file {vimrc} is read for initializations. Most other
initializations are skipped; see |initialization|. This can
be used to start Vim in a special mode, with special
mappings and settings. A shell alias can be used to make
this easy to use. For example:
alias vimc vim -u ~/.c_vimrc !*
So, when you want to start Vim with a custom vimrc, you can use:
$ vim -u {custom_vimrc}
But starting Vim like this will enable the 'compatible'
option:
Using the "-u" argument has the side effect that the
'compatible' option will be on by default. This can have
unexpected effects. See |'compatible'|.
… which is probably not what you want. To be sure 'compatible'
is disabled, you can add the -N
argument:
$ vim -Nu {custom_vimrc}
Finally, if your {custom_vimrc}
file is not on your local machine but on the web, you can use a process substitution, which appears to be:
a form of redirection where the input or output of a process (some
sequence of commands) appear as a temporary file.
One of the possible syntax using process substitution seems to be:
$ shell_command <( <LIST> )
… where <LIST>
is a command list.
You could use this to make the output of the shell command curl url
appear as a temporary file to vim -Nu
.
So, maybe you could start Vim from your shell with a command like this:
$ vim -Nu <(curl url)
For example:
$ vim -Nu <(curl https://raw.githubusercontent.com/tpope/vim-sensible/master/plugin/sensible.vim)
$ vim -Nu <(curl url)