On 26/03/11 07:49, [email protected] wrote:
Hi,
via www.vim.org I found a script, which converts gui-only color
schemes on-the-fly into cterm color schemes.
It processes the the original colorscheme when it gets read
via
:ColorScheme<gui-colorscheme-name>
instead of
:colorscheme<gui-colorscheme-name>
Normally I set my preferred color scheme via .vimrc (Linux).
But: It seems, that when .vimrc is read there are no scripts are
installed/active/read because the command "ColorScheme" in
:ColorScheme<name>
in the .vimrc produces a "Not an editor command"-error.
Is there a way to circumvent this without a too big hack?
Thank you very much in advance for any help!
Have a nice weekend!
Best regards
mcc
Either
invoke the script by sourcing it in your vimrc (before the ColorScheme
command) *instead* of having the script in a plugin/ subdirectory of
some directory in 'runtimepath' (so the script will be sourced sooner)
Or
put your ColorScheme command in a VimEnter autocommand (so the command
will be run later).
The command :scriptnames outputs one line per script, in the order these
scripts were sourced. (If a script was sourced more than once it is
listed only the first time, and there is no indication of when a script
finished being sourced.)
Best regards,
Tony.
--
$3,000,000
--
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
