[doc][patch] Update documents of Charles' plugins

2019-12-08 Fir de Conversatie Ken Takata
Hi Charles and Bram, I found some mistakes in the documents of Charles' plugins. Could you check and merge the attached patch? Regards, Ken Takata -- -- 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 informat

Odd display bug with gVim under Windows

2019-12-08 Fir de Conversatie Christian J. Robinson
Load the attached file in gVim and you should see the line of "x" characters display higher than they should. For me on my recent compile they display so high that they interfere with the top line of the buffer displaying the alphabet. This appears to happen when the line contains the one or

Re: [vim/vim] Highlight the line number columns of not-current windows independently (#5332)

2019-12-08 Fir de Conversatie Christian Brabandt
How about scripting and changing the highlighting around a WinLeave autocommand? > Am 08.12.2019 um 23:20 schrieb Leonardo (Vim Github Repository) > : > >  > Is your feature request related something that is currently hard to do? > Please describe. > > I would like to be able to highlight the

Re: Upcoming Vim 8.2 release

2019-12-08 Fir de Conversatie nickspoons
On Saturday, 30 November 2019 10:13:22 UTC+13, Bram Moolenaar wrote: > > I'm also wondering: what is your favorite improvement since Vim 8.1? > I'm also really enjoying the popups. I have a screencast here, but it demonstrates a problem rather than acts as a showcase I think: https://asciinema.

[patch] fixed typos in doc

2019-12-08 Fir de Conversatie Dominique Pellé
Hi Attached patch fixes a few typos in the documentation. Regards 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 mess

Re: [vim/vim] gvim spamming console from which it was started (#3628)

2019-12-08 Fir de Conversatie John Little
On Monday, December 9, 2019 at 2:58:29 AM UTC+13, Juan Lanus wrote: ... Bit of a necro, out of the blue a year later... Anyway, I remember these nuisances, but they've been gone for me for some time, GTK2 or GTK3. I'm on Ubuntu 19.10. Maybe it's been fixed in GTK (if so I'd be surprised), or

Patch 8.1.2412

2019-12-08 Fir de Conversatie Bram Moolenaar
Patch 8.1.2412 Problem:Crash when evaluating expression with error. (Dhiraj Mishra) Solution: Check parsing failed. (closes #5329) Files: src/eval.c, src/testdir/test_lambda.vim *** ../vim-8.1.2411/src/eval.c 2019-12-01 21:11:18.433245377 +0100 --- src/eval.c 2019-12-08 18:34:52.20

Patch 8.1.2411

2019-12-08 Fir de Conversatie Bram Moolenaar
Patch 8.1.2411 Problem:Function argument copied unnecessarily. Solution: Use the argument directly. Files: src/ex_docmd.c *** ../vim-8.1.2410/src/ex_docmd.c 2019-12-01 21:41:24.477837841 +0100 --- src/ex_docmd.c 2019-12-08 17:06:08.074212014 +0100 *** *** 3412,3

Re: [vim/vim] gvim spamming console from which it was started (#3628)

2019-12-08 Fir de Conversatie Christian Brabandt
This looks like a GTK bug, so not sure what we can do here. But it is an open source project, so please feel welcome to contribute > Am 08.12.2019 um 14:58 schrieb Juan Lanus (Vim Github Repository) > : > >  > Any computer interactive application, whatever it is - like for example > onlin