Re: [vim/vim] sh.vim: Syntax highlighting thinks quote does not close (#1008)

On 2018-05-24, Gary Johnson wrote: > On 2018-05-24, cecamp wrote: > > > Please try the latest syntax/sh.vim from my website (v177):  > > http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH > > That's really nice! It fixes a problem I've seen for quite a while > with single-quotes/apostrophe

Re: [vim/vim] sh.vim: Syntax highlighting thinks quote does not close (#1008)

On 2018-05-24, cecamp wrote: > Please try the latest syntax/sh.vim from my website (v177):  > http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH That's really nice! It fixes a problem I've seen for quite a while with single-quotes/apostrophes within shell comments. Thank you. Regards, Ga

Re: Lua 5.4 32bits support

Le jeudi 24 mai 2018 15:21:34 UTC+2, Kazunobu Kuriyama a écrit : > On Wed, May 23, 2018 at 5:56 PM Ni Va wrote: > > Hi, > > > > On Windows 10, > > > > 1. After download and build lua 5.4 current work I got a the lua.5.4.0.dll 32 > bits and rename it to lua54.dll > > > > guidelines : >

Re: PuTTy connection to RHEL 6.9 mouse not usable on Vim 8.1.0022 startup

Another note: git bisect shows that the problem started somewhere around 8.0.1309, but I can't be sure becuase I can't build vim on this system for several commits in that range (the build errors out). -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply

PuTTy connection to RHEL 6.9 mouse not usable on Vim 8.1.0022 startup

On upgrading to the latest version of Vim, I noticed that starting Vim up results in a Vim session that doesn't respond to mouse clicks (cursor looks like "I"). I'd appreciate it if someone else could reproduce this error. Out put ":version"... VIM - Vi IMproved 8.1 (2018 May 17, compiled May 24

Re: Lua 5.4 32bits support

On Wed, May 23, 2018 at 5:56 PM Ni Va wrote: > Hi, > > On Windows 10, > > 1. After download and build lua 5.4 current work I got a the lua.5.4.0.dll > 32 bits and rename it to lua54.dll > > guidelines : > https://blog.spreendigital.de/2015/01/16/how-to-compile-lua-5-3-0-for-windows/ Is that art

Re: [vim/vim] balloon_show doesn't display the balloon (#2948)

On Do, 24 Mai 2018, h_east wrote: > Hi, > > 2018-5-24(Thu) 17:29:20 UTC+9 Christian Brabandt: > > Hm, it looks like BalloonEval is initially not set therefore skipping > > displaying the balloon. > > > > Shouldn't we need something like this? > > > > diff --git a/src/evalfunc.c b/src/evalfunc

Re: feature to differentiate 32 from 64 bits build version

On Thu, May 24, 2018 at 11:38 AM, Andreas wrote: > What about just testing sizeof(void *)==8 ? > Regards > anst That won't work, because we want a solution for vimscript, not for C: :echo sizeof(void *) E121: Undefined variable: void E116: Invalid arguments for function sizeof(void *) E15: Inval

:h jump-motions

Hi, I wonder if ":h jump-motions" needs updating. Some jump commands that aren't mentioned: :p :# :cn etc. gd etc. u * # [count]zz etc. zj etc. :goto Any movement under :g I don't know if that's an exhaustive list, or if some of those are considered to be cove

Re: feature to differentiate 32 from 64 bits build version

On Wednesday, 23 May 2018 15:33:37 UTC+2, Tony Mechelynck wrote: > On Wed, May 23, 2018 at 3:14 PM, Ken Takata wrote: > > Hi, > > > > 2018/5/23 Wed 21:29:43 UTC+9 Ni Va wrote: > >> I build both 32 and 64 bits version of gvim but always 1 is returned when > >> from 32bits or 64bits I do : > >> >

Re: [vim/vim] balloon_show doesn't display the balloon (#2948)

Hi, 2018-5-24(Thu) 17:29:20 UTC+9 Christian Brabandt: > Hm, it looks like BalloonEval is initially not set therefore skipping > displaying the balloon. > > Shouldn't we need something like this? > > diff --git a/src/evalfunc.c b/src/evalfunc.c > index 2793803b7..a1e243a9e 100644 > --- a/src/eva