Re: Vim 8 pre-announcement

2016-08-18 0:17 GMT+03:00 Bram Moolenaar : > > Skywind3000 wrote: > >> > Hello Vim users, >> > >> > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be >> > released in about two weeks. >> > >> > This is a last chance to modify new features in a way that is

Re: error in test_startup_utf8

Hi, 2016/8/18 Thu 5:36:51 UTC+9 Danek Duvall wrote: > On Wed, Aug 17, 2016 at 09:52:12PM +0200, Bram Moolenaar wrote: > > > Danek Duvall wrote: > > > > > I'm seeing this. It's on Solaris, but I'm not sure whether that matters, > > > or if it does, what aspect does. > > > > > > From

[patch] test62.{in,ok} convert to the new style test `test_tabpage.vim`

Hi Bram and list, Attach a patch. Please include this. -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Re: Vim 8 pre-announcement

Skywind3000 wrote: > > Hello Vim users, > > > > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be > > released in about two weeks. > > > > This is a last chance to modify new features in a way that is not > > backwards compatible. Once 8.0 is out we can't make changes that

Re: Vim 8 pre-announcement

Thinca wrote: > :help job-term says: > > *job-term* > "term": "open"Start a terminal and connect the job > stdin/stdout/stderr to it. > NOTE: Not implemented yet! > > This is not implemented yet. Is this not implemented in Vim 8.0? It

Re: Patch 7.4.2219

Andy Wokula wrote: > Am 16.08.2016 um 21:04 schrieb Bram Moolenaar: > > Patch 7.4.2219 > > Problem:Recursive call to substitute gets stuck in sandbox. (Nikolai > > Pavlov) > > Solution: Handle the recursive call. (Christian Brabandt, closes #950) > > Add a test. >

Re: Vim 8 pre-announcement

Andy Wokula wrote: > Am 16.08.2016 um 18:43 schrieb Bram Moolenaar: > > Hello Vim users, > > > > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be > > released in about two weeks. > > > > This is a last chance to modify new features in a way that is not > > backwards

Re: [patch] :make doesn't support encoding conversion

Ken Takata wrote: > I wrote a patch for the following todo item: > > > Win32: When running ":make" and 'encoding' differs from the system locale, > > the > > output should be converted. Esp. when 'encoding' is "utf-8". (Yongwei Wu) > > Should we use 'termencoding' for this? > > I think using

Re: Vim 8 pre-announcement

Yegappan Lakshmanan wrote: > On Wed, Aug 17, 2016 at 2:10 AM, 'Guyzmo' via vim_dev > wrote: > > On Wed, Aug 17, 2016 at 11:48:23AM +0300, LCD 47 wrote: > >> On 16 August 2016, Yegappan Lakshmanan wrote: > >> > getbufinfo() > >> "options",

Re: error in test_startup_utf8

On Wed, Aug 17, 2016 at 09:52:12PM +0200, Bram Moolenaar wrote: > Danek Duvall wrote: > > > I'm seeing this. It's on Solaris, but I'm not sure whether that matters, > > or if it does, what aspect does. > > > > From test_startup_utf8.vim: > > Found errors in Test_read_fifo_utf8(): > >

Re: [patch] fixed crash in sign command with deleted buffer

Dominique Pellé wrote: > Vim-7.4. and older segfaults with this command: > > $ vim -u NONE -S crash-sign-7.4..vim > > Vim: Caught deadly signal SEGV > > Vim: Finished. > Segmentation fault (core dumped) > > crash-sign-7.4..vim is the attached file. > > Bug was found

Re: [patch][doc] Fix typos

Ken Takata wrote: > 2016/8/17 Wed 9:52:24 UTC+9 Ken Takata wrote: > > Hi, > > > > Please check the attached patch for fixing typos in docs. > > And... the patches 7.4.2063 - 7.4.2162 in the list were duplicated. > > I think we need description for binary number. Thanks. -- I'm not familiar

Re: [patch][doc] Fix typos

Ken Takata wrote: > Please check the attached patch for fixing typos in docs. > And... the patches 7.4.2063 - 7.4.2162 in the list were duplicated. Thanks! -- One difference between a man and a machine is that a machine is quiet when well oiled. /// Bram Moolenaar -- b...@moolenaar.net --

Re: Vim 8 pre-announcement

Hello Bram, On 8/16/2016 6:43 PM, Bram Moolenaar wrote: > Hello Vim users, > > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be > released in about two weeks. > > This is a last chance to modify new features in a way that is not > backwards compatible. Once 8.0 is out we

Patch 7.4.2224

Patch 7.4.2224 Problem:Compiler warnings with older compiler and 64 bit numbers. Solution: Add "LL" to large values. (Mike Williams) Files: src/eval.c, src/evalfunc.c *** ../vim-7.4.2223/src/eval.c 2016-08-14 16:07:44.717705432 +0200 --- src/eval.c 2016-08-17 21:46:57.953745759

Re: error in test_startup_utf8

Danek Duvall wrote: > I'm seeing this. It's on Solaris, but I'm not sure whether that matters, > or if it does, what aspect does. > > From test_startup_utf8.vim: > Found errors in Test_read_fifo_utf8(): > function RunTheTest[9]..Test_read_fifo_utf8 line 24: Expected ['テスト', >

Re: [bug] write beyond end of string when calling feedkeys

Dominique wrote: > Valgrind shows a write beyond end of string > in Vim-7.4. (huge) and older when doing: > > $ vim -u NONE -N -S bug-feedkeys-7.4.7222.vim 2> log > > ... where bug-feedkeys-7.4.7222.vim is the one-line > attached file. Note that the file is in latin1 encoding > and my

Re: Vim 8 pre-announcement

On Wed, Aug 17, 2016 at 10:54:17AM -0700, Yegappan Lakshmanan wrote: > On Wed, Aug 17, 2016 at 2:10 AM, 'Guyzmo' via vim_dev > wrote: > > On Wed, Aug 17, 2016 at 11:48:23AM +0300, LCD 47 wrote: > >> On 16 August 2016, Yegappan Lakshmanan wrote: > >>

Re: Vim 8 pre-announcement

Hi, On Wed, Aug 17, 2016 at 4:12 AM, Michael Henry wrote: > On 08/17/2016 12:00 AM, Yegappan Lakshmanan wrote: >> I am in particular interested in any comments/suggestions about the > following >> new functions: >> >> getbufinfo() >> gettabinfo() >> getwininfo() >>

Re: Vim 8 pre-announcement

Hi, On Wed, Aug 17, 2016 at 2:10 AM, 'Guyzmo' via vim_dev wrote: > On Wed, Aug 17, 2016 at 11:48:23AM +0300, LCD 47 wrote: >> On 16 August 2016, Yegappan Lakshmanan wrote: >> > getbufinfo() >> "options", "signs", and "variables" return lists

Re: Vim 8 pre-announcement

Hi, On Wed, Aug 17, 2016 at 1:48 AM, LCD 47 wrote: > On 16 August 2016, Yegappan Lakshmanan wrote: >> I am in particular interested in any comments/suggestions about the following >> new functions: >> >> getbufinfo() > > From the manual: > > :

Re: Vim 8 pre-announcement

Am 16.08.2016 um 18:43 schrieb Bram Moolenaar: Hello Vim users, Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be released in about two weeks. This is a last chance to modify new features in a way that is not backwards compatible. Once 8.0 is out we can't make changes that

[patch] fixed crash in sign command with deleted buffer

Hi Vim-7.4. and older segfaults with this command: $ vim -u NONE -S crash-sign-7.4..vim Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault (core dumped) crash-sign-7.4..vim is the attached file. Bug was found using afl-fuzz. Attached patch fixes it, but I'm

Re: Vim 8 pre-announcement

On 08/17/2016 12:00 AM, Yegappan Lakshmanan wrote: > I am in particular interested in any comments/suggestions about the following > new functions: > > getbufinfo() > gettabinfo() > getwininfo() > getqflist() > setqflist() > getcompletion() I've got some custom functions in my .vimrc related to

Re: Vim 8 pre-announcement

On Wed, Aug 17, 2016 at 11:48:23AM +0300, LCD 47 wrote: > On 16 August 2016, Yegappan Lakshmanan wrote: > > getbufinfo() > "options", "signs", and "variables" return lists that are potentially > huge. Perhaps there should be a way to tell getbufinfo() to skip these

[bug] write beyond end of string when calling feedkeys

Hi Valgrind shows a write beyond end of string in Vim-7.4. (huge) and older when doing: $ vim -u NONE -N -S bug-feedkeys-7.4.7222.vim 2> log ... where bug-feedkeys-7.4.7222.vim is the one-line attached file. Note that the file is in latin1 encoding and my locale is en_US.UTF-8. log file

[patch] :make doesn't support encoding conversion

Hi, I wrote a patch for the following todo item: > Win32: When running ":make" and 'encoding' differs from the system locale, the > output should be converted. Esp. when 'encoding' is "utf-8". (Yongwei Wu) > Should we use 'termencoding' for this? I think using 'termencoding' for this is not so

Re: Vim 8 pre-announcement

On 16 August 2016, Yegappan Lakshmanan wrote: > I am in particular interested in any comments/suggestions about the following > new functions: > > getbufinfo() From the manual: : Each returned List item is a dictionary with the following :

Re: Vim 8 pre-announcement

Bram: > Hello Vim users, > > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be > released in about two weeks. > > This is a last chance to modify new features in a way that is not > backwards compatible. Once 8.0 is out we can't make changes that would > break plugins. Can

Re: Vim 8 pre-announcement

Hi Bram, 2016-08-17 1:43 GMT+09:00 Bram Moolenaar : > > Hello Vim users, > > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be > released in about two weeks. > > This is a last chance to modify new features in a way that is not > backwards compatible. Once