Re: version8.txt wrongly says that :wsverb command was added in vim-8.2

2019-12-30 Thread John Little
Just noticed that :help patches gives version8.txt, which lists all the patch descriptions since 7.4.1, 6,600 of them, but stops at 8.1.2424; there's no list for the 50 or so 8.2 patches. Now, version8.txt has become unwieldy; at 1.6 MB it's by far the largest file in the repo, and github gru

Re: version8.txt wrongly says that :wsverb command was added in vim-8.2

2019-12-30 Thread Bram Moolenaar
John Little wrote: > Just noticed that :help patches gives version8.txt, which lists all the > patch descriptions since 7.4.1, 6,600 of them, but stops at 8.1.2424; > there's no list for the 50 or so 8.2 patches. > > Now, version8.txt has become unwieldy; at 1.6 MB it's by far the largest

Re: Warning for 4 unused variables in scriptfile.c in Tiny and Small (only) after applying patches 8.1. 56 to 58

2019-12-30 Thread Bram Moolenaar
Tony wrote: > This is probably no problem, but… We like to keep the build warning-free! > gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/scriptfile.o > scriptfile.c > scriptfile.c: In function ‘estack_sfile’: > sc

Patch 8.2.0059

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0059 Problem:Compiler warnings for unused variables in small build. (Tony Mechelynck) Solution: Add #ifdef. Files: src/scriptfile.c *** ../vim-8.2.0058/src/scriptfile.c2019-12-29 23:52:58.585005552 +0100 --- src/scriptfile.c2019-12-30 10:55:05.848617132

Re: version8.txt wrongly says that :wsverb command was added in vim-8.2

2019-12-30 Thread Christian Brabandt
On Mo, 30 Dez 2019, Bram Moolenaar wrote: > > John Little wrote: > > > Just noticed that :help patches gives version8.txt, which lists all the > > patch descriptions since 7.4.1, 6,600 of them, but stops at 8.1.2424; > > there's no list for the 50 or so 8.2 patches. > > > > Now, version8.

Re: version8.txt wrongly says that :wsverb command was added in vim-8.2

2019-12-30 Thread John Little
On Tuesday, December 31, 2019 at 12:18:01 AM UTC+13, Bram Moolenaar wrote: >Opinions? I agree the info is useful; I noticed because I didn't find the 8.2.00* patch details. Just as there is presently version4.txt, 5, 6, 7, I suggest version7.4.txt, version8.0.txt, version8.1.txt and version

Patch 8.2.0060

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0060 Problem:Message test only runs with one encoding. (Dominique Pelle) Solution: Run the test with "utf-8" and "latin1". Fix underflow. (related to #5410) Files: src/message_test.c, src/message.c *** ../vim-8.2.0059/src/message_test.c 2019-12-21 18:25:50.453

RFC: Support for customizing the text displayed in the quickfix window

2019-12-30 Thread Yegappan Lakshmanan
Hi all, I have seen several requests for customizing the text displayed in the quickfix window. I am attaching the updates to the help text for adding a new "qfbufexpr" option that will support this. Any comments and suggestions on this approach? Regards, Yegappan diff --git a/runtime/doc/option

Re: RFC: Support for customizing the text displayed in the quickfix window

2019-12-30 Thread skywind3000
Please provide a `raw` reserved option for qfbufexpr, and if it is initialized as: set qbe=raw Just keep the original text and don't run any filter function ?? for the speed purpose. And I don't need to write a function! ReturnAsItIs(is_qf, qfid, eidx) if a:isqf le

Patch 8.2.0061

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0061 Problem:The execute stack can grow big and never shrinks. Solution: Reduce the size in gargage collect. Files: src/eval.c *** ../vim-8.2.0060/src/eval.c 2019-12-25 19:33:18.520594684 +0100 --- src/eval.c 2019-12-30 19:12:49.939679473 +0100 *** *** 3857,38

Re: RFC: Support for customizing the text displayed in the quickfix window

2019-12-30 Thread skywind3000
Or use one of: set qbe=* set qbe=$ set qbe=- set qbe=? to distinguish from function names ?? 在 2019年12月31日星期二 UTC+8上午2:20:37,skywind3000写道: > > Please provide a `raw` reserved option for qfbufexpr, and if it is > initialized as: > > set qbe=raw > > Just keep the original tex

Patch 8.2.0062

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0062 Problem:Memory test is flaky on FreeBSD. Solution: Add a short sleep before getting the first size. Files: src/testdir/test_memory_usage.vim *** ../vim-8.2.0061/src/testdir/test_memory_usage.vim 2019-08-07 22:05:40.0 +0200 --- src/testdir/test_memory_usage.v

Patch 8.2.0063

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0063 Problem:Wrong size argument to vim_snprintf(). (Dominique Pelle) Solution: Reduce the size by the length. (related to #5410) Files: src/ops.c *** ../vim-8.2.0062/src/ops.c 2019-12-17 22:10:54.564370706 +0100 --- src/ops.c 2019-12-30 20:37:38.566321032 +0100 ***

Patch 8.2.0064

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0064 Problem:Diffmode completion doesn't use per-window setting. Solution: Check if a window is in diff mode. (Dominique Pell, closes #5419) Files: src/buffer.c, src/testdir/test_diffmode.vim *** ../vim-8.2.0063/src/buffer.c2019-12-29 23:04:20.290639897 +0100 --- sr

Patch 8.2.0065

2019-12-30 Thread Bram Moolenaar
Patch 8.2.0065 Problem:Amiga and alikes: autoopen only used on Amiga OS4. Solution: Adjust #ifdefs. (Ola Söder, closes #5413) Files: src/os_amiga.c *** ../vim-8.2.0064/src/os_amiga.c 2019-12-05 20:15:14.0 +0100 --- src/os_amiga.c 2019-12-30 22:26:16.175684071 +0100

Re: version8.txt wrongly says that :wsverb command was added in vim-8.2

2019-12-30 Thread Christian Brabandt
On Mo, 30 Dez 2019, Bram Moolenaar wrote: > > John Little wrote: > > > Just noticed that :help patches gives version8.txt, which lists all the > > patch descriptions since 7.4.1, 6,600 of them, but stops at 8.1.2424; > > there's no list for the 50 or so 8.2 patches. > > > > Now, version8.

Re: version8.txt wrongly says that :wsverb command was added in vim-8.2

2019-12-30 Thread Dominique Pellé
Christian Brabandt wrote: > On Mo, 30 Dez 2019, Bram Moolenaar wrote: > > > > > John Little wrote: > > > > > Just noticed that :help patches gives version8.txt, which lists all the > > > patch descriptions since 7.4.1, 6,600 of them, but stops at 8.1.2424; > > > there's no list for the 50 or so 8

Re: buffer number and python interface

2019-12-30 Thread Ernie Rael
On 12/29/2019 6:11 PM, Ernie Rael wrote: From python, is it *always* true that "vim.buffer[i].number == i" ? -ernie I've convinced myself that this is true. The docs say A mapping object providing access to the list of vim buffers. ... b.number    Buffer number. Can be used as |pytho

Re: buffer number and python interface

2019-12-30 Thread Tony Mechelynck
On Tue, Dec 31, 2019 at 3:31 AM Ernie Rael wrote: > > On 12/29/2019 6:11 PM, Ernie Rael wrote:root > > From python, is it *always* true that "vim.buffer[i].number == i" ? > > > > -ernie > > > I've convinced myself that this is true. The docs say > > A mapping object providing access to the lis

Re: buffer number and python interface

2019-12-30 Thread Tony Mechelynck
On Tue, Dec 31, 2019 at 3:48 AM Ernie Rael wrote: > > On 12/30/2019 6:42 PM, Tony Mechelynck wrote: > > On Tue, Dec 31, 2019 at 3:31 AM Ernie Rael wrote: > >> On 12/29/2019 6:11 PM, Ernie Rael wrote:root > >>> From python, is it *always* true that "vim.buffer[i].number == i" ? > >>> > >>> -ernie

Re: buffer number and python interface

2019-12-30 Thread Ernie Rael
On 12/30/2019 7:05 PM, Tony Mechelynck wrote: On Tue, Dec 31, 2019 at 3:48 AM Ernie Rael wrote: On 12/30/2019 6:42 PM, Tony Mechelynck wrote: On Tue, Dec 31, 2019 at 3:31 AM Ernie Rael wrote: On 12/29/2019 6:11 PM, Ernie Rael wrote:root From python, is it *always* true that "vim.buffer[i]