Re: vim-win32-installer build on appveyor failed

On Fr, 22 Mär 2019, Christian Brabandt wrote: > > On Fr, 22 Mär 2019, Bram Moolenaar wrote: > > > How about with patch 1033 included? > > This came to late, but the problem test 1033 fixed, did not appear on > the appveyor build. And the build with patch 1032 worked perfectly > again: > htt

Re: Changed behaviour with comments

Ah, thanks Gary, now it makes sense! I didn't realise the autocmd pattern could match different things. The examples in the docs use BufRead, hence always matching file names. Thanks for taking the time to explain it to me. Rob. On Wed, 27 Mar 2019 at 01:50, Gary Johnson wrote: > On 2019-03-

Patch 8.1.1057

Patch 8.1.1057 Problem:Nsis config is too complicated. Solution: Use "File /r" for the macros and pack directories. (Ken Takata, closes #4169) Files: nsis/gvim.nsi *** ../vim-8.1.1056/nsis/gvim.nsi 2019-02-19 21:40:22.617135352 +0100 --- nsis/gvim.nsi 2019-03-

Patch 8.1.1056

Patch 8.1.1056 Problem:No eval function for Ruby. Solution: Add rubyeval(). (Ozaki Kiichi, closes #4152) Files: runtime/doc/eval.txt, runtime/doc/if_ruby.txt, src/evalfunc.c, src/if_ruby.c, src/proto/if_ruby.pro, src/testdir/test_ruby.vim *** ../vim-8.1.1055/runtime/doc/e

Patch 8.1.1055

Patch 8.1.1055 Problem:CTRL-G U in Insert mode doesn't work to avoid splitting the undo sequence for shift-left and shift-right. Solution: Also check dont_sync_undo for shifted cursor keys. (Christian Brabandt) Files: src/edit.c, src/testdir/test_mapping.vim *

Re: [patch] make U work with /

Christian wrote: > Bram, > I noticed a thread in reddit¹ about how to avoid breaking the undo > sequence in insert mode with . I thought U should do it, > but it didn't work, so I looked it up and noticed we need some special > handling there as well. > > Please see the attached patch. It ad

Re: [bug] vim on windows does not seem to expand environment variables

On 2019-03-26, Christian Brabandt wrote: > On Di, 26 Mär 2019, Gary Johnson wrote: > > > On 2019-03-26, Charles Cooper wrote: > > > > ... neither of the following work: > > > > :echo expand("$PATH") > > > This works for me now as it has in the past, using a gvim compiled with > > > MSVC. Could

Re: [bug] vim on windows does not seem to expand environment variables

On Di, 26 Mär 2019, Bram Moolenaar wrote: > expand() wasn't made for expanding environment variables. Why not use > $PATH directly? because I was trying to use an environment variable that is not know to Vim :) > Not sure if $random works, might be something built into cmd.exe. Yes it is.

Re: [bug] vim on windows does not seem to expand environment variables

On Di, 26 Mär 2019, Gary Johnson wrote: > On 2019-03-26, Charles Cooper wrote: > > > ... neither of the following work: > > > :echo expand("$PATH") > > This works for me now as it has in the past, using a gvim compiled with > > MSVC. Could there be a difference if compiled with gcc? > > Thi

Re: [bug] vim on windows does not seem to expand environment variables

Christian wrote: > having read :h expand-env, I suspected that this also works on Windows, > however it does not seem to be the case: > > :echo $PATH > " This correctly shows the path, but neither of the following work: > :echo expand("$PATH") > :echo expand("%PATH%") > > My use case is to ha

Patch 8.1.1054

Patch 8.1.1054 Problem:Not checking return value of ga_grow(). (Coverity) Solution: Only append when ga_grow() returns OK. Files: src/if_lua.c *** ../vim-8.1.1053/src/if_lua.c2019-03-23 13:56:30.189804811 +0100 --- src/if_lua.c2019-03-26 21:40:15.851115489 +0100 *

Re: [bug] vim on windows does not seem to expand environment variables

On 2019-03-26, Charles Cooper wrote: > > ... neither of the following work: > > :echo expand("$PATH") > This works for me now as it has in the past, using a gvim compiled with > MSVC. Could there be a difference if compiled with gcc? This works for me, too, using the latest Windows gvim that I

Re: [bug] vim on windows does not seem to expand environment variables

> ... neither of the following work: > :echo expand("$PATH") This works for me now as it has in the past, using a gvim compiled with MSVC. Could there be a difference if compiled with gcc? > :echo expand("%PATH%") Agree this does not work. Charlie -- -- You received this message from the

[bug] vim on windows does not seem to expand environment variables

Hi, having read :h expand-env, I suspected that this also works on Windows, however it does not seem to be the case: :echo $PATH " This correctly shows the path, but neither of the following work: :echo expand("$PATH") :echo expand("%PATH%") My use case is to have cmd.exe return a pseudo random

[patch] make U work with /

Bram, I noticed a thread in reddit¹ about how to avoid breaking the undo sequence in insert mode with . I thought U should do it, but it didn't work, so I looked it up and noticed we need some special handling there as well. Please see the attached patch. It adds a test as well. Furthermore it

Re: Changed behaviour with comments

On 2019-03-27, Robert Webb wrote: > Wow, that did the trick somehow. > > Using "h,c,cpp" as the file pattern works, but not "*.h,*.c,*.cpp" as per the > examples in the docs, and as I've been using for years up till now. > > Why?  Is this only required for FileType and not BufRead? > > And won't

Re: Changed behaviour with comments

Wow, that did the trick somehow. Using "h,c,cpp" as the file pattern works, but not "*.h,*.c,*.cpp" as per the examples in the docs, and as I've been using for years up till now. Why? Is this only required for FileType and not BufRead? And won't "h,c,cpp" match ANY file containing a "c" or an "