Re: .TXT FILES MODIFIED AT OPENING W/ GVIM ON WINDOWS 10

2020-08-14 Fir de Conversatie John Sellers
I got around to quite a bit of experimenting today, and I am getting inconsistent results. I apologize, but I didn't set up a case testing scenario to clearly and unambiguously sort out the behavior. My test-beds for gvim --clean -R filename and gvim filename in Powershell. In Windows 10 the

Patch 8.2.1456

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1456 Problem:MS-Windows: test files are not deleted. Solution: use "del" instead of $(DEL). Files: src/testdir/Make_dos.mak *** ../vim-8.2.1455/src/testdir/Make_dos.mak2020-08-14 19:20:19.790506736 +0200 --- src/testdir/Make_dos.mak2020-08-14 23:06:50.447082524

Patch 8.2.1455

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1455 Problem:Vim9: crash when using typecast before constant. Solution: Generate constant before checking type. Add tets. Files: src/vim9compile.c, src/testdir/test_vim9_expr.vim *** ../vim-8.2.1454/src/vim9compile.c 2020-08-14 22:16:29.586423086 +0200 ---

Patch 8.2.1454

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1454 Problem:Vim9: failure invoking lambda with wrong arguments. Solution: Handle invalid arguments. Add a test. Files: src/vim9compile.c, src/vim9execute.c, src/testdir/test_vim9_expr.vim *** ../vim-8.2.1453/src/vim9compile.c 2020-08-14 21:42:50.823581047

Patch 8.2.1453

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1453 Problem:Vim9: failure to compile lambda not tested. Solution: Add a test case. Files: src/testdir/test_vim9_expr.vim *** ../vim-8.2.1452/src/testdir/test_vim9_expr.vim 2020-08-14 21:27:34.097321673 +0200 --- src/testdir/test_vim9_expr.vim 2020-08-14

Patch 8.2.1452

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1452 Problem:Vim9: dead code in to_name_end(). Solution: Remove check for lambda and dict, it won't be used. Files: src/vim9compile.c *** ../vim-8.2.1451/src/vim9compile.c 2020-08-13 22:47:20.373992741 +0200 --- src/vim9compile.c 2020-08-14 21:41:35.460062535 +0200

Patch 8.2.1451

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1451 Problem:Vim9: list type at script level only uses first item. Solution: Use all members, like in a compiled function. (closes #6712) Also for dictionary. Files: src/vim9type.c, src/testdir/test_vim9_expr.vim *** ../vim-8.2.1450/src/vim9type.c

Patch 8.2.1450

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1450 Problem:Vim9: no check that script-local items don't become global. Solution: Add a test. Files: src/testdir/test_vim9_script.vim *** ../vim-8.2.1449/src/testdir/test_vim9_script.vim2020-08-14 17:08:12.008859508 +0200 --- src/testdir/test_vim9_script.vim

Patch 8.2.1449

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1449 Problem:Some test makefiles delete files that are not generated. Solution: Remove the deletion commands. Files: src/testdir/Make_dos.mak, src/testdir/Make_ming.mak, src/testdir/Make_amiga.mak, src/testdir/Make_vms.mms ***

Patch 8.2.1448

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1448 Problem:Test 77a for VMS depends on small.vim which does not exist. Solution: Use the 'silent while 0" trick. (issue #6696) Files: src/testdir/test77a.in *** ../vim-8.2.1447/src/testdir/test77a.in 2014-03-12 15:55:50.0 +0100 --- src/testdir/test77a.in

Patch 8.2.1447

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1447 Problem:Vim9: return type of keys() is list. Solution: Should be list. (closes #6711) Files: src/evalfunc.c, src/testdir/test_vim9_func.vim *** ../vim-8.2.1446/src/evalfunc.c 2020-08-12 21:34:43.266489468 +0200 --- src/evalfunc.c 2020-08-14

Patch 8.2.1446

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1446 Problem:Vim9: line number in error message is not correct. Solution: Set SOURCING_LNUM before calling emsg(). (closes #6708) Files: src/vim9execute.c, src/testdir/test_vim9_func.vim *** ../vim-8.2.1445/src/vim9execute.c 2020-08-13 22:47:20.377992734 +0200 ---

Re: Bulk ftplugin updates - browsefilter GTK support

2020-08-14 Fir de Conversatie Doug Kearns
On Sat, 15 Aug 2020 at 00:44, Bram Moolenaar wrote: > > Doug Kearns wrote: > > > I've noticed that most of the ftplugins that support browsefilter don't > > test for the "gui_gtk" feature. > > > > Is there a process in place for executing bulk ftplugin updates in a case > > like this or should I

Patch 8.2.1445

2020-08-14 Fir de Conversatie Bram Moolenaar
Patch 8.2.1445 Problem:Vim9: function expanded name is cleared when sourcing a script again. Solution: Only clear the expanded name when deleting the function. (closes #6707) Files: src/userfunc.c, src/testdir/test_vim9_script.vim ***

Re: Bulk ftplugin updates - browsefilter GTK support

2020-08-14 Fir de Conversatie Bram Moolenaar
Doug Kearns wrote: > I've noticed that most of the ftplugins that support browsefilter don't > test for the "gui_gtk" feature. > > Is there a process in place for executing bulk ftplugin updates in a case > like this or should I just contact all the maintainers? I'm afraid contacting the

Re: .TXT FILES MODIFIED AT OPENING W/ GVIM ON WINDOWS 10

2020-08-14 Fir de Conversatie Tony Mechelynck
On Fri, Aug 14, 2020 at 1:36 PM John Sellers wrote: > > This is happening on my new month year old computer as well as my 10+ year > old computer. > > The behavior is exactly the same on both computers when using Gvim to open a > .txt file. (I have not checked other kinds of files). > > While

.TXT FILES MODIFIED AT OPENING W/ GVIM ON WINDOWS 10

2020-08-14 Fir de Conversatie John Sellers
This is happening on my new month year old computer as well as my 10+ year old computer. The behavior is exactly the same on both computers when using Gvim to open a .txt file. (I have not checked other kinds of files). While looking at the file in a Windows explorer directory in detail

Bulk ftplugin updates - browsefilter GTK support

2020-08-14 Fir de Conversatie Doug Kearns
G'day all, I've noticed that most of the ftplugins that support browsefilter don't test for the "gui_gtk" feature. Is there a process in place for executing bulk ftplugin updates in a case like this or should I just contact all the maintainers? Thanks, Doug -- -- You received this message