On 21 мар, 20:08, Tony Mechelynck <[email protected]>
wrote:
> On 18/03/09 10:26, Maxim Kim wrote:
>
> See ":help E10" and check your backslashes. Also, what does
>
> :verbose set cp?
> (with the question mark) tell you?
nocompatible
Last set from ~\_vimrc
>
> Anyway, the safest way to run a (possibly long) vimscript is to source
> it after having saved it. Why don't you want to save your script?
Usually I do save & source my script files. But sometimes there are
moments I want to test some vimscript. So I create a new buffer, write
and test functions there and if everything is ok I move them into my
script file.
It is also really convenient to tune colorschemes -- add bunch of
colors for a single group:
hi Identifier guibg=#e8f0e0 guifg=#306010 gui=none
hi Identifier guibg=#e8f0d0 guifg=#306010 gui=italic
hi Identifier guibg=#e8f0c0 guifg=#306010 gui=bold
hi Identifier guibg=#e8f0b0 guifg=#306010 gui=none
Try every highlight and choose preffered one.
Anyway the following mappings work for me (without longlines)
" run selected vimscript
vmap <Leader>r "vy:@v<CR>
" run vimscript line
nmap <Leader>r "vyy:@v<CR>
PS
Is the next command Ex one?
map <C-d> ihello
\world<ESC>
If it is, shouldn't 2yy:@" command run it flawlessly?
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
