Patch 7.4.1215

Patch 7.4.1215 Problem:Using old style function declarations. Solution: Change to new style function declarations. (script by Hirohito Higashi) Files: src/version.c, src/winclip.c, src/window.c, src/workshop.c, src/xpm_w32.c, runtime/doc/doctags.c,

Patch 7.4.1216

Patch 7.4.1216 Problem:Still using HAVE_STDARG_H. Solution: Assume it's always defined. Files: src/eval.c, src/misc2.c, src/vim.h, src/proto.h, src/congifure.in, src/auto/configure, config.h.in, src/os_amiga.h, src/os_msdos.h, src/os_vms_conf.h, src/os_win32.h

Re: 7.4.1207 fails to build

Elimar Riesebieter wrote: > Huge build on linux: > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " " __TIME__ ")"; >^ > version.c:52:56: warning: macro

Re: Updating runtime files without version control

Ken Takata wrote: > Hi Christian, > > 2016/1/28 Thu 18:10:37 UTC+9 Christian Brabandt wrote: > > Hi Ken! > > > > On Do, 28 Jan 2016, Ken Takata wrote: > > > > > Hi Christian, > > > > > > 2016/1/28 Thu 15:52:54 UTC+9 Christian Brabandt wrote: > > > > Hi Ken! > > > > > > > > On Mi, 27 Jan

[patch] fixed compilation error in gui_motif.c

Hi Attached patch fixes the following compilation error with the Motif GUI with vim-7.4.1210: $ gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MOTIF -g -O2 -Wall -Wshadow -Wmissing-prototypes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DEXITFREE-o objects/gui_motif.o gui_motif.c ...

Re: [patch] fixed compilation error in gui_motif.c

Dominique Pellé wrote: > Attached patch fixes the following compilation > error with the Motif GUI with vim-7.4.1210: > > $ gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MOTIF -g -O2 -Wall > -Wshadow -Wmissing-prototypes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3D1 > -DEXITFREE-o

Patch 7.4.1212

Patch 7.4.1212 (after 7.4.1207) Problem:Can't build with Motif. Solution: Fix function declaration.(Dominique Pelle) Files: src/gui_motif.c *** ../vim-7.4.1211/src/gui_motif.c 2016-01-30 16:39:20.438376481 +0100 --- src/gui_motif.c 2016-01-30 19:43:51.575263364 +0100

Re: [patch] more __ARGS

Hirohito Higashi wrote: > Hi tux and Bram, > > 2016-1-30(Sat) 8:29:34 UTC+9 tux.: > > Now it compiles with all the features again ;-) > > Thanks for the patch. > A little more corresponding file will increase in my environment. > > On fedora Linux. > > $ cd vim > $ git fetch . > $ git

Re: Compiling 1202 with OLE=yes fails

Axel Bender wrote: > with > > gcc -c -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF > -DFEAT_BIG -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT > -DFEAT_OLE -DFEAT_CSCOPE -DFEAT_CHANNEL -DF > EAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME

Re: 7.4.1207 fails to build

* Bram Moolenaar [2016-01-30 18:11 +0100]: > > Elimar Riesebieter wrote: > > > > Huge build on linux: > > > > > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > > > [-Wdate-time] > > > char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " "

Re: Updating runtime files without version control

Hi Christian, 2016/1/28 Thu 18:10:37 UTC+9 Christian Brabandt wrote: > Hi Ken! > > On Do, 28 Jan 2016, Ken Takata wrote: > > > Hi Christian, > > > > 2016/1/28 Thu 15:52:54 UTC+9 Christian Brabandt wrote: > > > Hi Ken! > > > > > > On Mi, 27 Jan 2016, Ken Takata wrote: > > > > > > > Now I can

Re: Updating runtime files without version control

Hi Ken! On Sa, 30 Jan 2016, Ken Takata wrote: > Has the setup of https://github.com/vim/vim-win32-installer been completed? > It seems almost perfect except that the appveyor badge is broken. Yes I think it is completed now. I think Bram will announce it soon. I also noticed the broken badge.

7.4.1207 fails to build

Huge build on linux: on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds [-Wdate-time] char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " " __TIME__ ")"; ^ version.c:52:56: warning: macro "__TIME__" might prevent reproducible

Re: 7.4.1207 fails to build

* Elimar Riesebieter [2016-01-30 17:06 +0100]: > Huge build on linux: > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " " __TIME__ ")"; >

Re: 7.4.1207 fails to build

* Bram Moolenaar [2016-01-30 17:32 +0100]: > > Elimar Riesebieter wrote: > > > Huge build on linux: > > > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > > [-Wdate-time] > > char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " " __TIME__ ")";

Re: 7.4.1207 fails to build

Elimar Riesebieter wrote: > > Huge build on linux: > > > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > > [-Wdate-time] > > char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " " __TIME__ ")"; > >^ > > version.c:52:56:

Patch 7.4.1209

Patch 7.4.1209 (after 7.4.1207) Problem:Can't build with Athena. (Elimar Riesebieter) Solution: Fix function declarations. Files: src/gui_athena.c, src/gui_x11.c, src/gui_at_sb.c, src/gui_at_fs.c *** ../vim-7.4.1208/src/gui_athena.c2016-01-30 16:39:20.430376564 +0100 ---

Compiling 1202 with OLE=yes fails

with gcc -c -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF -DFEAT_BIG -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_OLE -DFEAT_CSCOPE -DFEAT_CHANNEL -DF EAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w

Re: Compiling 1202 with OLE=yes fails

Addendum: Windows 7 64bit MinGW -- -- 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 because you are subscribed to the Google

Adding highlight groups for relative numbers

All, Shaun Brady here. Thanks for the best text editor! I had a simple want, and I believe I have achieved this with the attached patch. I wanted my relative line numbers to be colored differently above and below the cursor line. I believe a highlight group applied conditionally is the

Patch 7.4.1204

Patch 7.4.1204 Problem:Latin1 characters cause encoding conversion. Solution: Remove the characters. Files: src/gui_motif.c *** ../vim-7.4.1203/src/gui_motif.c 2016-01-29 22:13:26.051781481 +0100 --- src/gui_motif.c 2016-01-30 13:51:29.850650765 +0100 *** ***

Patch 7.4.1203

Patch 7.4.1203 Problem:Still more files still using __ARGS. Solution: Remove __ARGS in really the last files. Files: src/proto/if_mzsch.pro, src/if_mzsch.c, src/vim.h, src/proto/gui_gtk_gresources.pro, src/proto/gui_mac.pro, src/proto/if_ole.pro,

Re: Patch 7.4.1202

Tux wrote: > Bram Moolenaar schrob am Freitag, 29. Januar 2016 um 23:46 Zeit: > > > Patch 7.4.1202 > > Problem:Still one more file still using __ARGS. > > Solution: Remove __ARGS in the last file. > > No, close to last ... :-) you missed proto/if_mzsch.pro Looks like my search for

Re: type of number/float in vim script

Ken Takata wrote: > 2016/1/25 Mon 8:13:42 UTC+9 Ken Takata wrote: > > Hi, > > > > 2016/1/22 Fri 21:00:16 UTC+9 Ken Takata wrote: > > > 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

Re: [win32][patch] Updated large file patches

Hi, 2016/1/30 Sat 12:51:11 UTC+9 Ken Takata wrote: > Hi, > > 2016/1/21 Thu 7:11:51 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > 2016/1/20 Wed 7:47:18 UTC+9 Ken Takata wrote: > > > > Hi Bram, > > > > > > > > 2016/1/20 Wed 3:33:18 UTC+9 Bram Moolenaar wrote: > > > > > Ken Takata

Re: [win32][patch] Updated large file patches

Hi, 2016/1/31 Sun 0:02:07 UTC+9 Ken Takata wrote: > Hi, > > 2016/1/30 Sat 12:51:11 UTC+9 Ken Takata wrote: > > Hi, > > > > 2016/1/21 Thu 7:11:51 UTC+9 Bram Moolenaar wrote: > > > Ken Takata wrote: > > > > > > > 2016/1/20 Wed 7:47:18 UTC+9 Ken Takata wrote: > > > > > Hi Bram, > > > > > > > > >

After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

At patchlevel 7.4.1219, I see the following messages in Tiny compile but not in Huge. They "may" be due to a different (recent but earlier) patchlevel: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_cmds.o ex_cmds.c

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

(When writing to Japanese posters, I never know which is the given name and which is the family name: I know that the Japanese custom is to put the family name first, but some Japanese people reverse their names when writing to "Western" people and some not, and I never know which is which. Please

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

Hi Tony, 2016-1-31(Sun) 10:14:15 UTC+9 Tony Mechelynck: > (When writing to Japanese posters, I never know which is the given > name and which is the family name: I know that the Japanese custom is > to put the family name first, but some Japanese people reverse their > names when writing to

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

Hi Tony, 2016-1-31(Sun) 8:21:26 UTC+9 Tony Mechelynck: > At patchlevel 7.4.1219, I see the following messages in Tiny compile > but not in Huge. They "may" be due to a different (recent but earlier) > patchlevel: > > gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall >

Patch 7.4.1217

Patch 7.4.1217 Problem:Execution of command on channel doesn't work yet. Solution: Implement the "ex" and "normal" commands. Files: src/channel.c, src/proto/channel.pro, src/misc2.c, src/eval.c, src/ex_docmd.c, src/proto/ex_docmd.pro, src/feature.h ***

Coding style changed? Not in the help

The coding style of C function declarations seems to have undergone a massive change yesterday (well, I'm on CET = GMT+0100 and it's shortly after midnight my time). However, runtime/doc/develop.txt lines 327-345 (about half a screen _above_ ":help style-spaces") still reflect the "old" Vim

Re: Patch 7.4.1215

Hi Bram! 2016-1-31(Sun) 5:30:20 UTC+9 Bram Moolenaar: > Patch 7.4.1215 > Problem:Using old style function declarations. > Solution: Change to new style function declarations. (script by Hirohito > Higashi) > Files: src/version.c, src/winclip.c, src/window.c, src/workshop.c,

crash with modifying v:errors

Hi list. let v:['errors'] = 123 call assert_equal(1,2) This make vim crash because list_unref expect VV_LIST. It's solve with change type VV_RO for VV_ERRORS, but docs says To remove old results make it empty: > :let v:errors = [] So I fixed to call list_unref safe for another

Patch 7.4.1218

Patch 7.4.1218 Problem:Missing change in configure. More changes for function style. Solution: Avoid the typos. Files: src/configure.in, src/config.h.in, runtime/tools/ccfilter.c, src/os_msdos.c *** ../vim-7.4.1217/src/configure.in2016-01-28 15:34:21.931646199 +0100

Patch 7.4.1219

Patch 7.4.1219 Problem:Build fails with +channel but without +float. Solution: Add #ifdef. Files: src/ex_cmds.c *** ../vim-7.4.1218/src/ex_cmds.c 2016-01-30 15:52:42.567439563 +0100 --- src/ex_cmds.c 2016-01-30 23:35:40.185570496 +0100 *** *** 520,526

Re: Coding style changed? Not in the help

Hi Tony, 2016-1-31(Sun) 8:38:43 UTC+9 Tony Mechelynck: > The coding style of C function declarations seems to have undergone a > massive change yesterday (well, I'm on CET = GMT+0100 and it's shortly > after midnight my time). > > However, runtime/doc/develop.txt lines 327-345 (about half a

Re: display of listchars characters on the cursorline & visual-mode

On Tuesday, November 25, 2014 at 11:15:11 PM UTC-2, mattn wrote: > On Wednesday, November 26, 2014 9:34:27 AM UTC+9, mattn wrote: > > Bram, It's a definite bug, and he provides awesome fix. Let's merge which > > one! > > presuku updated above patch. This patch is better than above. > >

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

On 31-Jan-16, Tony Mechelynck wrote: > (When writing to Japanese posters, I never know which is the given > name and which is the family name: I know that the Japanese custom is > to put the family name first, but some Japanese people reverse their > names when writing to "Western" people and some

Re: [vim] has("patch-7.3.867") return 0. (#615)

On Sun, Jan 31, 2016 at 4:59 AM, Wang Shidong wrote: > > but my vim --version show me > > VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:47) > 包含补丁: 1-52 Regardless of which version you are running (in this case: 7.4.52), has('patch-7.3.867') will

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

On 31-Jan-16, Tony Mechelynck wrote: > (When writing to Japanese posters, I never know which is the given > name and which is the family name: I know that the Japanese custom is > to put the family name first, but some Japanese people reverse their > names when writing to "Western" people and some

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

On Sun, Jan 31, 2016 at 2:35 AM, h_east wrote: > Hi Tony, > > 2016-1-31(Sun) 10:14:15 UTC+9 Tony Mechelynck: >> (When writing to Japanese posters, I never know which is the given >> name and which is the family name: I know that the Japanese custom is >> to put the family

Re: [vim] has("patch-7.3.867") return 0. (#615)

On Sun, Jan 31, 2016 at 6:16 AM, Tony Mechelynck wrote: > On Sun, Jan 31, 2016 at 4:59 AM, Wang Shidong > wrote: >> >> but my vim --version show me >> >> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:47) >> 包含补丁: 1-52 > >

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

On Sun, Jan 31, 2016 at 6:17 AM, Kazunobu Kuriyama wrote: > On 31-Jan-16, Tony Mechelynck wrote: >> (When writing to Japanese posters, I never know which is the given >> name and which is the family name: I know that the Japanese custom is >> to put the family name

Re: After bringing source up-to-date to 7.4.1219, compile warnings in Tiny but not in Huge

On 31-Jan-16, Olaf Dabrunz wrote: > On 31-Jan-16, Tony Mechelynck wrote: > > (When writing to Japanese posters, I never know which is the given > > name and which is the family name: I know that the Japanese custom is > > to put the family name first, but some Japanese people reverse their > >

Re: [vim] has("patch-7.3.867") return 0. (#615)

Hi, 2016-1-31(Sun) 13:25:00 UTC+9 Wang Shidong: > it is in > > https://github.com/artur-shaik/vim-javacomplete2/blob/f7a0a6e175011be95500452ba7a4cc510fd940dd/autoload/javacomplete.vim#L200-L202 > > > if has("patch-7.3.867") > autocmd TextChangedI *.java,*.jsp call s:HandleTextChangedI() >