Le samedi 13 décembre 2014 20:23:22 UTC+1, Enno a écrit :
To use Vim under powershell in MS Windows, set shell=powershell and
shellcmdflag=-c.
However, if shell=powershell and shellcmdflag=-c, then tempname() returns a
file name with forward slashes because 'powershell' contains 'sh' and
Using autochdir in .vimrc together with the --remote-silent start option works
fine: the first edited file's path is set correctly.
However, the manuals suggest not to use autochdir:
This option is provided for backward compatibility with the Vim released with
Sun ONE Studio 4 Enterprise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16-Dec-2014 14:30, Axel Bender wrote:
Using autochdir in .vimrc together with the --remote-silent start
option works fine: the first edited file's path is set correctly.
However, the manuals suggest not to use autochdir:
This option is
On 20:11 Sat 13 Dec , Bram Moolenaar wrote:
Marcin Szamotulski wrote:
I attach the promised patch for checking if the range is invalid.
Thanks!
Updated version, I figured out that 0 range is needed for :tabe.
Best regards,
Marcin
--
--
You received this message from the vim_dev