On 26.02.16 08:29, Roman wrote:
> I use ':.w !sh' to run some lines with shell commands
> Is any way to transfer output of this commands back to buffer or maybe
> to split buffer window or do something like ':r !sh $current_line'
The easiest way to return the result is not to use ":.w", but the !
Hi,
I have just compiled Vim with +Python/dyn feature but when I start my vim own
distri that uses omnisharp, this says :
Error Desktop\Vim\awesomeplugins\omnisharp-vim-master\plugin\OmniSharp.vim :
ligne2 :
Error: OmniSharp requires Vim compiled with +python.
When I call :ver from
Hi Dominique and Luc,
thanks you for the advice. I agree that it is not a good idea to blindly
replace everything. The most common case for me is probably static_cast so I
would do that by default.
> In lh-cpp (*), I have 3 mappings that transform C casts into C++ casts -- and
> 6 more to
Hi, Ken, thanks for the reply.
I have no vimrc/.vimrc/_vimrc in both $HOME. Anything in $HOME that connects to
vim is _viminfo. This is just a history file.
My gvim is in d:\vim\vim74. And in both cases output of :scriptnames have the
same line "d:\vim\_vimrc".
And here's how I start gvim in
Hi,
2016/2/28 Sun 2:18:54 UTC+9 Alexas Chee wrote:
> Yes, the _vimrc is the same one.
>
> $HOME is different, though. The Windows one is C:\user\myname; the mingw64
> one is msys2/home/myname.
>
> But does $HOME matter in this case?
Vim will load .vimrc from $HOME. So you might get different
Hi,
Yes, the _vimrc is the same one.
$HOME is different, though. The Windows one is C:\user\myname; the mingw64 one
is msys2/home/myname.
But does $HOME matter in this case?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you
Ben Fritz wrote:
> On Friday, February 26, 2016 at 12:02:42 PM UTC-6, Bram Moolenaar wrote:
> > Christian Brabandt wrote:
> > >
> > > Really a plugin directory is necessary? That sounds awkward. What about
> > > colorschemes, indent or ftplugins and syntax scripts?
> > >
> > > We could still
