Patch 8.2.4417

2022-02-18 Fir de Conversatie Bram Moolenaar
Patch 8.2.4417 (after 8.2.4416) Problem:Using NULL pointer. Solution: Set offset after checking for NULL pointer. Files: src/userfunc.c *** ../vim-8.2.4416/src/userfunc.c 2022-02-18 17:50:00.445462060 + --- src/userfunc.c 2022-02-18 18:33:34.405033096 +

Patch 8.2.4416

2022-02-18 Fir de Conversatie Bram Moolenaar
Patch 8.2.4416 Problem:Vim9: using a script-local function requires using "s:" when setting 'completefunc'. Solution: Do not require "s:" in Vim9 script. (closes #9796) Files: runtime/doc/options.txt, src/userfunc.c, src/testdir/test_ins_complete.vim *** ../vi

Re: Mingw-make Building Vim.8.2.4398 causes error

2022-02-18 Fir de Conversatie Ni Va
Thank you ! Bram :) Le vendredi 18 février 2022 à 14:58:18 UTC+1, Bram Moolenaar a écrit : > > > Here are my flags > > > > FLAGS="OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes > LUA=./$LuaDir/src > > LUA_VER=54 \ > > PYTHON3=$Python3Dir DYNAMIC_PYTHON3=yes PYTHON3_VER=311 > > DYNAMIC_PY

Patch 8.2.4415

2022-02-18 Fir de Conversatie Bram Moolenaar
Patch 8.2.4415 Problem:Function argument name conflicts with C++ keyword. Solution: Rename the argument. Files: src/usercmd.c, src/proto/usercmd.pro *** ../vim-8.2.4414/src/usercmd.c 2022-02-16 12:44:26.129908861 + --- src/usercmd.c 2022-02-18 13:55:44.914231893 +

Re: Mingw-make Building Vim.8.2.4398 causes error

2022-02-18 Fir de Conversatie Bram Moolenaar
> Here are my flags > > FLAGS="OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes LUA=./$LuaDir/src > LUA_VER=54 \ > PYTHON3=$Python3Dir DYNAMIC_PYTHON3=yes PYTHON3_VER=311 > DYNAMIC_PYTHON3_DLL=python311.dll \ > RUBY=$RubyDir DYNAMIC_RUBY=yes RUBY_VER=31 RUBY_API_VER_LONG=3.1

Patch 8.2.4414

2022-02-18 Fir de Conversatie Bram Moolenaar
Patch 8.2.4414 Problem:Solidity files are not recognized. Solution: Add the *.sol pattern. (Dundar Goc, closes #9792) Files: runtime/filetype.vim, src/testdir/test_filetype.vim *** ../vim-8.2.4413/runtime/filetype.vim2022-02-17 21:30:22.227126637 + --- runtime/filetype.v

Patch 8.2.4413

2022-02-18 Fir de Conversatie Bram Moolenaar
Patch 8.2.4413 Problem:Vim9: Coverity warns for using NULL pointer. Solution: Give an internal error when funcref function can't be found. Files: src/vim9execute.c *** ../vim-8.2.4412/src/vim9execute.c 2022-02-17 19:44:04.271319375 + --- src/vim9execute.c 2022-02-18 13:23:18.

Re: Mingw-make Building Vim.8.2.4398 causes error

2022-02-18 Fir de Conversatie Ni Va
Here are my flags FLAGS="OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes LUA=./$LuaDir/src LUA_VER=54 \ PYTHON3=$Python3Dir DYNAMIC_PYTHON3=yes PYTHON3_VER=311 DYNAMIC_PYTHON3_DLL=python311.dll \ RUBY=$RubyDir DYNAMIC_RUBY=yes RUBY_VER=31 RUBY_API_VER_LONG=3.1.0 -I/c/Ruby31-

Re: def! in legacy vimscript

2022-02-18 Fir de Conversatie Ben Jackson
OK, makes sense, thanks. > On 18 Feb 2022, at 11:29, Bram Moolenaar wrote: > > >>> Wether a function is script-local or global (when not using a "s:" or >>> "g:" prefix) depends on the script it's defined in The rule is "at the >>> script level, the type of script defines what the scope of the

Patch 8.2.4412

2022-02-18 Fir de Conversatie Bram Moolenaar
Patch 8.2.4412 Problem:Translation cleanup script does not remove empty lines at end. Solution: Remove empty lines at the end. (Ken Takata, closes #9794) Files: src/po/cleanup.vim *** ../vim-8.2.4411/src/po/cleanup.vim 2017-07-16 19:29:27.0 +0100 --- src/po/cleanup.vim 2022

Re: def! in legacy vimscript

2022-02-18 Fir de Conversatie Bram Moolenaar
> > Wether a function is script-local or global (when not using a "s:" or > > "g:" prefix) depends on the script it's defined in The rule is "at the > > script level, the type of script defines what the scope of the items > > is". I think that's easy to understand. > > You know, I think the oth

Re: def! in legacy vimscript

2022-02-18 Fir de Conversatie puremo...@gmail.com
> Wether a function is script-local or global (when not using a "s:" or "g:" prefix) depends on the script it's defined in > The rule is "at the script level, the type of script defines what the scope of the items is". I think that's easy to understand. You know, I think the other rule is argu