On Sun, Mar 1, 2015 at 4:05 PM, Bao Niu <niubao56@gmail.com> wrote:
> These days I seem never use non-GUI vim. I don't worry not being able to use something that is only for non-GUI, could someone give a list of commands that MUST be put into .vimrc?
>
> If there is no such limitation, is it safe to come to the conclusion that I can just throw everyting to .gvimrc? That would be a lot neater than having two files. thanks.
No, it isn't.
When gvim starts, it loads .vimrc before loading plugins, and .gvimrc
after all plugins have been loaded. You won't be able to customize
some plugins if you put all your configuration inside .gvimrc instead
of .vimrc.
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> 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 vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
--
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 http://www.vim.org/maillist.php
---
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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment