Re: Update to vim CMake syntax files

Dimitri Merejkowsky wrote: > I did a bit of research and discovered that CMake maintains their own vim > files here: > https://cmake.org/download/ > > So not sure what the process is in this case. Do we sync manually the files > from cmake's repo to vim's repo or do we let distro packagers

Patch 7.4.1153

Patch 7.4.1153 Problem:Autocommands triggered by quickfix cannot always get the current title value. Solution: Call qf_fill_buffer() later. (Christian Brabandt) Files: src/quickfix.c, src/testdir/test_quickfix.vim *** ../vim-7.4.1152/src/quickfix.c 2016-01-21

Re: Patch 7.4.718

Christian Brabandt wrote: > On Mo, 04 Mai 2015, Bram Moolenaar wrote: > > > Patch 7.4.718 > > Problem:Autocommands triggered by quickfix cannot get the current title > > value. > > Solution: Set w:quickfix_title earlier. (Yannick) > > Also move the check for a

Re: [if_perl][patch] Improve I/O integration

Hi Christian Le Fri, Jan 22, 2016 at 10:40:04AM -0700, Christian J. Robinson a écrit : > On Fri, 22 Jan 2016, Damien wrote: > > >I updated this patch with v7.4.1152. > > It compiles and functions properly, but I do get a couple of warnings for > the usage of char: > > proto/syntax.pro:43:5:

[tabnext/tabprevious] {count} inconsistency

Hi, I think, there is an inconsistency with regard to the :tabnext and :tabprev commands: :tabn[ext] {count} {count} {count}gt Go to tab page {count}. The first tab page has number one. :tabp[revious] {count} :tabN[ext] {count} {count} {count}gT Go {count} tab pages back. Wraps

Re: [tabnext/tabprevious] {count} inconsistency

Hi Tony! On Fr, 22 Jan 2016, Tony Mechelynck wrote: > On Fri, Jan 22, 2016 at 12:43 PM, Tony Mechelynck > wrote: > > On Fri, Jan 22, 2016 at 12:04 PM, Christian Brabandt > > wrote: > >> Hi, > >> I think, there is an inconsistency with regard

Re: [tabnext/tabprevious] {count} inconsistency

Hi Tony! On Fr, 22 Jan 2016, Tony Mechelynck wrote: > On Fri, Jan 22, 2016 at 12:04 PM, Christian Brabandt > wrote: > > Hi, > > I think, there is an inconsistency with regard to the :tabnext and > > :tabprev commands: > > > > > > :tabn[ext] {count} > > {count} > > {count}gt

Re: [tabnext/tabprevious] {count} inconsistency

On Fri, Jan 22, 2016 at 12:43 PM, Tony Mechelynck wrote: > On Fri, Jan 22, 2016 at 12:04 PM, Christian Brabandt > wrote: >> Hi, >> I think, there is an inconsistency with regard to the :tabnext and >> :tabprev commands: >> >> >> :tabn[ext]

Re: Patch 7.4.718

Hi Bram! On Mo, 04 Mai 2015, Bram Moolenaar wrote: > > Patch 7.4.718 > Problem:Autocommands triggered by quickfix cannot get the current title > value. > Solution: Set w:quickfix_title earlier. (Yannick) > Also move the check for a title into the function. > Files:

Re: [if_perl][patch] Improve I/O integration

Hi list, > Damien wrote: > The attached patch add a minimal implementation of PerlIO Layer > feature and try to use it for STDOUT/STDERR. I updated this patch with v7.4.1152. Regards, Damien -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below

Re: [tabnext/tabprevious] {count} inconsistency

On Fri, Jan 22, 2016 at 12:04 PM, Christian Brabandt wrote: > Hi, > I think, there is an inconsistency with regard to the :tabnext and > :tabprev commands: > > > :tabn[ext] {count} > {count} > {count}gt Go to tab page {count}. The first tab page has number one. > >

Re: type of number/float in vim script

Hi, 2016/1/21 Thu 21:48:44 UTC+9 Ken Takata wrote: > Hi mattn and all, > > I think that supporting 64-bit Number (even on 32-bit systems) is very useful. > One of the best examples is getfsize() as mattn said. 32-bit Number is too > small to represent a filesize nowadays. > > > 2014/1/6 Mon

Re: Updating runtime files without version control

Ken Takata wrote: > OK, I added a note: > https://github.com/k-takata/vim-win32-installer/releases > > I think it's ready to set up the official installer repository. Thanks for setting that up. It will be of great benefit. However, can the explanatory text be improved? If each release has to

Re: Updating runtime files without version control

Hi Bram and Christian, 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > Hi Bram, > > > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote: > > > I am including the changes to gvim.nsi. I also updated the code to look > > > for libintl-8.dll, since that one uses the

Re: Patch 7.4.1133

Hirohito Higashi wrote: > Hi Bram! > > 2016-1-22(Fri) 4:24:57 UTC+9 Bram Moolenaar: > > Hirohito Higashi wrote: > > > > > 2016-1-21(Thu) 6:48:27 UTC+9 Bram Moolenaar: > > > > Hirohito Higashi wrote: > > > > > > > > > Hi Bram and Vimmers! > > > > > > > > > > 2016-1-20(Wed) 3:00:59 UTC+9 Bram

Re: [if_perl][patch] Improve I/O integration

On Fri, 22 Jan 2016, Damien wrote: I updated this patch with v7.4.1152. It compiles and functions properly, but I do get a couple of warnings for the usage of char: proto/syntax.pro:43:5: note: expected ‘char_u *’ but argument is of type ‘char *’ if_perl.xs:719:1: note: expected ‘char_u

Re: Updating runtime files without version control

Hi Bram, 2016/1/23 Sat 6:58:13 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > Hi Bram and Christian, > > > > 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote: > > > Ken Takata wrote: > > > > > > > Hi Bram, > > > > > > > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote: > > > > > I am

Re: Plugins - Vim licence?

On Fri, 22 Jan 2016, David Fishburn wrote: When plugins are developed and made available on the Vim website, do they adopt the Vim licence? The authors choose the license. Generally they adopt the Vim license, or another "open source compatible" license; I've seen some with GPL, some with