Re: Digest for - 1 update in 1 topic

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: Digest for - 1 update in 1 topic

Steve Brock
Check out gVim for Windows at  Portable apps are designed to run anywhere off a USB drive.   So don't install in Windows.  Just put the files in a folder somewhere on your hard drive.  It runs out of the folder and keeps the configuration files there.  But you can still make it a default app for handling particular file types.  8.2 is the most recent version there.

On Mon, Mar 9, 2020 at 1:43 AM <[hidden email]> wrote:
Tony Mechelynck <[hidden email]>: Mar 08 08:25AM +0100

> Hey, guys I recently started a position that requires me to use a windows workstation but I would like to have access to vim and the plugins I normally would use. I feel infinitely slower doing basic tasks without it. I managed to install the windows version but I am not fully understanding where the vimrc file belongs and how to get plug up and running with it so I can configure things and utilize plugins. Any tips or suggestions are appreciated. So far I have tried modifying the _vimrc in my x86 programs file and added the autoload directory like the Plug installation requires. But when I launch vim it doesn't seem to be recognizing my _vimrc changes or location maybe.
On Unix Vim looks for a startup file named .vimrc, on Windows for one
named _vimrc. In both cases it looks for it in your home directory —
and if $HOME (or, in Windows parlance, %HOME%) is not defined on
fallback location. If the vimrc is not found there, Vim looks for it
on Unix as ~/.vim/vimrc or on Windows as ~/vimfiles/vimrc (i.e., in
the latter case, %HOME%\vimfiles\vimrc or
%HOMEDRIVE%%HOMEPATH%\vimfiles\vimrc). Note that a vimrc in .vim (for
Unix) or in vimfiles (for Windows) must NOT have a . or _ at the start
of its filename.
All this, and more (e.g. how to invoke Vim so as to disregard an
existing vimrc) is explained under ":help vimrc".
For the plugins, they are in the plugin/ subdirectory (for global
plugins) of one of the directories mentioned in the 'runtimepath'
option. These are normally the following:
$HOME/.vim/ (Unix) or $HOME/vimfiles/ (Windows) for user-specific full scripts
$VIM/vimfiles/ for system-wide scripts, usually put there by a system
$VIMRUNTIME/ _only_ for scripts distributed together with Vim. Any Vim
update may silently modify them.
$VIM/vimfiles/after/ for system-wide snippets overriding any of the above
$HOME/.vim/after/ (Unix) or $HOME/vimfiles/after/ (Windows) for
user-specific snippets overriding any of the above.
All these five directory trees have the same layout, and if a script
looked-for in one of them is absent, it is no error: the result is the
same as if the script had been present but empty. In the case of
global plugins, however, all of them are sourced in the order they are
found, unless you disable them all by means of a command-line switch
which can take several forms, see ":help --noplugin".
In addition, you may have "packages" which add additional directories
to the above five.
:help 'runtimepath'
:help packages
:help plugin (which is a whole chapter about the various kinds
of plugins)
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].

You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit

You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit