Tom Smith <tom@...
> Will removing this file (mswin.vim) cause any side effects? It seems
> to be causing some wierd problems that, when run as "gvim -u NONE -U
> NONE", are no longer present.
The effects it will cause are:
- error if some script tries to source it
- Ctrl-V, Ctrl-X and Ctrl-C will regain their "Vim" meanings, and lose (in
Vim) their "Windows" meanings, which are related to clipboard cut-and-paste.
But you should be able do achieve the same in a much less drastic way, by
finding where that script is sourced (the listing from the :scriptnames
command shows all scripts sourced, in the order in which they were sourced),
and remove the "source" command there. (I still have mswin.vim on my system
but I don't use it.) AFAIK, the "standard" scripts that come with the vim
distribution don't invoke mswin.vim.