Re: Cannot find helptag :[range]

Hello Tony, Tony Mechelynck schrieb am 07.02.2017 um 02:00: > The helptag :[range] is defined at line 334 of helpfile motion.txt. > But it cannot be found. When I do > > :help :[range] > > I get to helptag :r instead, at line 1901 of helpfile insert.txt, and > that even after doing

Cannot find helptag :[range]

The helptag :[range] is defined at line 334 of helpfile motion.txt. But it cannot be found. When I do :help :[range] I get to helptag :r instead, at line 1901 of helpfile insert.txt, and that even after doing ":helptags $VIMRUNTIME/doc" and even by selecting :[range] in the wildmenu on (for

Re: Tests for the getcmdtype(), getcmdpos() and getcmdline() functions

Hi Bram, On Mon, Feb 6, 2017 at 1:23 PM, Bram Moolenaar wrote: > > Yegappan wrote: > >> I am attaching a patch to add tests for the getcmdtype(), getcmdpos() >> and getcmdline() functions. > > Thanks! > > There appears to be a one second delay in this test somewhere. > Can't

Patch 8.0.0314

Patch 8.0.0314 Problem:getcmdtype(), getcmdpos() and getcmdline() are not tested. Solution: Add tests. (Yegappan Lakshmanan) Files: src/testdir/test_cmdline.vim *** ../vim-8.0.0313/src/testdir/test_cmdline.vim2017-02-03 21:19:00.289942006 +0100 ---

Re: Tests for the getcmdtype(), getcmdpos() and getcmdline() functions

Yegappan wrote: > I am attaching a patch to add tests for the getcmdtype(), getcmdpos() > and getcmdline() functions. Thanks! There appears to be a one second delay in this test somewhere. Can't quite see where it happens. -- SIGIRO -- irony detected (iron core dumped) /// Bram Moolenaar

Re: [patch] Update help doc for GTK3 GUI.

Kazunobu Kuriyama wrote: > Attached is a patch to update eval.txt and options.txt to adjust them to > the addition of GTK3 GUI. Thanks! -- FROG: How you English say: I one more time, mac, I unclog my nose towards you, sons of a window-dresser, so, you think you could out-clever us

Patch 8.0.0313

Patch 8.0.0313 (after 8.0.0310) Problem:Not enough testing for GUI functionality. Solution: Add tests for the GUI font. (Kazunobu Kuriyama) Files: src/testdir/test_gui.vim *** ../vim-8.0.0312/src/testdir/test_gui.vim2017-02-05 20:54:21.772818426 +0100 ---

Re: [patch] Add tests on getfontname() to test_gui

Kazunobu Kuriyama wrote: > Attached is a patch to add two tests on getfontname() to test_gui. > > Since I have no idea on how font match/selection is done on platforms other > than X11, the tests are written to skip themselves on those platforms for > the present. > > The patch fixes some

Patch 8.0.0312

Patch 8.0.0312 Problem:When a json message arrives in pieces, the start is dropped and the decoding fails. Solution: Do not drop the start when it is still needed. (Kay Zheng) Add a test. Reset the timeout when something is received. Files: src/channel.c,

Re: Channel callbacks randomly fail to fire in Vim for win32

Kay Zheng wrote: > I did some research on the channel code, and if I read it right, > there's an issue in channel_fill(...). > > AFAIK, a channel in JSON mode works like this: > > 1. When a network message arrives, it tries to parse a complete JSON object. > 2. If there were a complete JSON

Re: [patch] fixed small mistakes in documentation

Charles E Campbell wrote: > Dominique Pellé wrote: >> Hi >> >> Attached patch fixes a few minor mistakes in help files. >> >> Dominique >> > regardless vs irregardless -- doesn't matter, really; "irregardless" is > a commonly used albeit non-standard word (that appears, btw, in several >

Re: [patch] fixed small mistakes in documentation

Dominique Pellé wrote: > Hi > > Attached patch fixes a few minor mistakes in help files. > > Dominique > regardless vs irregardless -- doesn't matter, really; "irregardless" is a commonly used albeit non-standard word (that appears, btw, in several dictionaries). About "thirty-two" vs "thirty

Re: [vim/vim] sh.vim: Feature request - Better processing of bash's substring expansion (#1437)

Norman Abramovitz wrote: > > Tried out 168 and still seeing the error. > > Uploading some screenshots showing the error colorization. Also > uploaded some highlight colorization showing that colorization is an > error colorization. > > screen shot 2017-02-06 at 9 30 39 am >

[patch] fixed small mistakes in documentation

Hi Attached patch fixes a few minor mistakes in help files. Dominique -- -- 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 http://www.vim.org/maillist.php --- You received this message

Re: [vim/vim] sh syntax highlighting should ignore "[" in echo lines (#1445)

matthew-cline wrote: > > If a syntax highlighted sh or bash script echoes out unbalanced "["s, > like with ANSI color codes > , this > will mess up highlighting until balancing "]"s are placed in > non-quoted, non-commented code. The

[patch] Update help doc for GTK3 GUI.

Hi, Attached is a patch to update eval.txt and options.txt to adjust them to the addition of GTK3 GUI. Best regards, Kazunobu Kuriyama -- -- 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

[patch] Add tests on getfontname() to test_gui

Hi, Attached is a patch to add two tests on getfontname() to test_gui. Since I have no idea on how font match/selection is done on platforms other than X11, the tests are written to skip themselves on those platforms for the present. The patch fixes some awkwardness in style I made with the

[patch] Update help doc for GTK3 GUI.

Hi, Attached is a patch to update eval.txt and options.txt to adjust them to the addition of GTK3 GUI. Best regards, Kazunobu Kuriyama -- -- 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: Channel callbacks randomly fail to fire in Vim for win32

Hi folks, I did some research on the channel code, and if I read it right, there's an issue in channel_fill(...). AFAIK, a channel in JSON mode works like this: 1. When a network message arrives, it tries to parse a complete JSON object. 2. If there were a complete JSON object, it saves the