date:20160823

tuxproject builds

2016-08-23 Thread zeug

As I know some of you are using them: My hoster has been experiencing 
serious DDoS attacks over the past few days, the data center finally 
decided to lock out non-European traffic to mitigate the attacks. If you 
wondered why I disappeared: I haven't. :-)


I don't know when it will be over, sorry. They're doing their best.

Regards.

--
--
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 Groups "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: compiler warning w/ Studio & gtk3 GUI

2016-08-23 Thread Kazunobu Kuriyama

2016-08-23 4:45 GMT+09:00 Danek Duvall :

> I'm seeing these warnings when building on Solaris with the Studio
> compilers.
>
> "gui_gtk_f.c", line 507: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void : 
> "/usr/include/glib-2.0/gobject/gsignal.h",
> line 431
> argument : pointer to function(void) returning void
> "gui_gtk_f.c", line 510: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void : 
> "/usr/include/glib-2.0/gobject/gsignal.h",
> line 431
> argument : pointer to function(void) returning void
> "gui_gtk_f.c", line 795: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void : 
> "/usr/include/glib-2.0/gobject/gsignal.h",
> line 431
> argument : pointer to function(void) returning void
> "gui_gtk_f.c", line 797: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void : 
> "/usr/include/glib-2.0/gobject/gsignal.h",
> line 431
> argument : pointer to function(void) returning void
> "gui_beval.c", line 522: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void : 
> "/usr/include/glib-2.0/gobject/gsignal.h",
> line 431
> argument : pointer to function(void) returning void
> "gui_beval.c", line 536: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void : 
> "/usr/include/glib-2.0/gobject/gsignal.h",
> line 431
> argument : pointer to function(void) returning void
>
> Frankly, it seems like it's a gtk/glib mismatch, since all the mechanism
> comes from those headers: GTK_SIGNAL_FUNC is G_CALLBACK, which just casts
> its argument to GCallback, which is the function pointer mentioned above,
> while the function prototype for gtk_signal_disconnect_by_func() takes a
> gpointer, which is the void *.
>

Hi Danek,

I think that mismatch is not our fault, either.

It looks strange that gtk/glib relies on an implicit conversion from a
pointer to function types to the generic pointer of object types, which is
not necessarily guaranteed to work on every platform.

That said, it would take some time to file the issue against them and wait
for their response to that; it would be better for us to do something about
that for ourselves.

So I made a patch for fixing the issue, which is attached to this mail.

For that, I assumed that the Solaris Studio had the predefined constant
macro __SUNPRO_C.  Is that assumption OK?

If that's OK, could you try the patch to check if it works as expected?

Note that the patch includes some minor fixes on coding style, too.


> glib is 2.46, gtk3 is 3.18.
>
> I don't see this in the travis logs, but I can't tell from there what
> versions of glib and gtk are in use.
>
> Does this look familiar to anyone?
>

I didn't see either clang or gcc (generic one, not the one which is a
symbolic link to clang) giving me any warning on the mismatch.  I didn't
know about that until I read you report.

Best regards,
Kazunobu

>
> Thanks,
> Danek
>
> --
> --
> 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 Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


solaris-studio-gtk3-warnings.patch
Description: Binary data

Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Elimar Riesebieter

Executed 162 tests¬
  1 FAILED:¬
  From test_alot.vim:
  Found errors in Test_tabpage_with_tab_modifier():¬
  function RunTheTest[9]..Test_tabpage_with_tab_modifier[13]..39_check_tab 
line 4: Expected 'help' but got 'text'

Repeated 9 times.


Elimar
-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread h_east

Hi Elimar,

2016-8-23(Tue) 18:28:18 UTC+9 Elimar Riesebieter:
> Executed 162 tests¬
>   1 FAILED:¬
>   From test_alot.vim:
>   Found errors in Test_tabpage_with_tab_modifier():¬
>   function 
> RunTheTest[9]..Test_tabpage_with_tab_modifier[13]..39_check_tab line 4: 
> Expected 'help' but got 'text'
> 
> Repeated 9 times.

Tell me your Vim configuration.
result of `:ver`.

--
Best regards,
Hirohito Higashi (a.k.a. h_east)

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] termguicolors doesn't work in terminal Vim (#993)

2016-08-23 Thread Ken Takata

Hi Christian,
(off topic)

2016/8/23 Tue 18:50:35 UTC+9 vim-dev ML wrote:
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.

The link "mute the thread" is still here.
I think the link should be removed.

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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Elimar Riesebieter

* h_east  [2016-08-23 02:36 -0700]:

> Hi Elimar,
> 
> 2016-8-23(Tue) 18:28:18 UTC+9 Elimar Riesebieter:
> > Executed 162 tests¬
> >   1 FAILED:¬
> >   From test_alot.vim:
> >   Found errors in Test_tabpage_with_tab_modifier():¬
> >   function 
> > RunTheTest[9]..Test_tabpage_with_tab_modifier[13]..39_check_tab line 
> > 4: Expected 'help' but got 'text'
> > 
> > Repeated 9 times.
> 
> Tell me your Vim configuration.
> result of `:ver`.

I tried to build 7.4.2243 which failed with the above messages. So
why do you want to know which version I am running? This has IMHO
nothing to do with a compile run ;-)

Elimar
-- 
  Do you smell something burning or is it me?

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [patch] :make doesn't support encoding conversion

2016-08-23 Thread Ken Takata

Hi Bram,

2016/8/22 Mon 2:29:28 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
> 
> > > > > > I wrote a patch for the following todo item:
> > > > > > 
> > > > > > > Win32: When running ":make" and 'encoding' differs from the 
> > > > > > > system locale, the
> > > > > > > output should be converted.  Esp. when 'encoding' is "utf-8". 
> > > > > > > (Yongwei Wu)
> > > > > > > Should we use 'termencoding' for this?
> > > > > > 
> > > > > > I think using 'termencoding' for this is not so good.  Normally
> > > > > > the encoding of a command output is the same as the encoding of
> > > > > > the terminal, but not always the same.  I hear that some commands
> > > > > > on Windows use utf-8 instead of the current codepage.  So I added
> > > > > > a new option 'cmdencoding' ('cenc').
> > > > > > What do you think of this?
> > > > > 
> > > > > Seems reasonable.  It's not nice that it's yet another option.  But in
> > > > > case you know the compiler output is in a certain encoding it's the 
> > > > > only
> > > > > way to make it work.
> > > > > 
> > > > > Why they "char" value?  It's using the system locale, wouldn't 
> > > > > "system"
> > > > > be better?  Hmm, I don't see where "char" is recognized.
> > > > 
> > > > At least, GNU libiconv supports "char".
> > > > 
> > > > See: https://www.gnu.org/software/libiconv/
> > > > | Locale dependent, in terms of `char' or `wchar_t' (with machine 
> > > > dependent
> > > > | endianness and alignment, and with OS and locale dependent semantics)
> > > > | char, wchar_t
> > > > | The empty encoding name "" is equivalent to "char": it denotes 
> > > > the locale
> > > > | dependent character encoding.
> > > > 
> > > > I don't know about other iconv implementations.
> > > 
> > > I found a few, but they all say that the name supported are system
> > > dependent.  Perhaps someone can dig deeper?
> > 
> > I hear that the "char" encoding would be a GNU extension. So the description
> > in options.txt would be:
> > 
> > This would be mostly useful when you use MS-Windows and set 'encoding'
> > to "utf-8".  If GNU libiconv is available, setting 'cmdencoding' to
> > "char" has the same effect as setting to the system locale encoding.
> > Example: >
> > :set encoding=utf-8
> > :set cmdencoding=char   " system locale is used
> > 
> > On Japanese Windows, `set cenc=char` has the same effect as `set 
> > cenc=cp932`.
> > (I suppose the Vim 8.0 win32 installer will contain GNU libiconv.)
> 
> Looking at this patch, I think it also applies the conversion to
> ":cbuffer".  That should not happen.  Also ":cexpr".

No, the conversion will not be applied to `:cbuffer` and `:cexpr`.
As I wrote in the help, it will be applied to:
`:make`, `:lmake`, `:grep`, `:lgrep`, `:grepadd`, `:lgrepadd`,
`:cfile`, `:cgetfile`, `:caddfile`, `:lfile`, `:lgetfile`, and
`:laddfile`.
(Oh, I didn't mention 'cenc' in each of them, only in `:make` and `:lmake`.)

My patch only adds the conversion to the function qf_get_next_file_line()
which is used only when reading from a file. (Note that `:make` and `:grep`
also use a file.)
Hm, is it confusing that 'cmdencoding' also applies to `:[cl].*file`?

`:cbuffer` calls qf_get_next_buf_line(), I think.


> In general, whether the conversion is needed depends on the command
> used.  E.g. for :grep and :make it might be different.  Not sure how to
> deal with that.

Do you mean `:grep` and `:make` should have different encoding options?
Maybe a user can create wrapper commands which set 'cenc' before executing
`:grep` or `:make`.
Of course, it would be nice if Vim supports it natively, but I have no idea
how to implement it.

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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread h_east

Hi Elimar,

2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter:
> * h_east [2016-08-23 02:36 -0700]:
> 
> > Hi Elimar,
> > 
> > 2016-8-23(Tue) 18:28:18 UTC+9 Elimar Riesebieter:
> > > Executed 162 tests¬
> > >   1 FAILED:¬
> > >   From test_alot.vim:
> > >   Found errors in Test_tabpage_with_tab_modifier():¬
> > >   function 
> > > RunTheTest[9]..Test_tabpage_with_tab_modifier[13]..39_check_tab line 
> > > 4: Expected 'help' but got 'text'
> > > 
> > > Repeated 9 times.
> > 
> > Tell me your Vim configuration.
> > result of `:ver`.
> 
> I tried to build 7.4.2243 which failed with the above messages. So
> why do you want to know which version I am running? This has IMHO
> nothing to do with a compile run ;-)

No, It has to do.
Please paste the result of `:ver` like below.

8<
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 22 2016 21:06:10)
Included patches: 1-2239
Compiled by h_east@localhost.localdomain
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):
+acl +file_in_path+mouse_sgr   +tag_old_static
+arabic  +find_in_path-mouse_sysmouse  -tag_any_white
+autocmd +float   +mouse_urxvt -tcl
+balloon_eval+folding +mouse_xterm +termguicolors
+browse  -footer  +multi_byte  +terminfo
++builtin_terms  +fork()  +multi_lang  +termresponse
+byte_offset +gettext -mzscheme+textobjects
+channel -hangul_input+netbeans_intg   +timers
+cindent +iconv   +num64   +title
+clientserver+insert_expand   +packages+toolbar
+clipboard   +job +path_extra  +user_commands
+cmdline_compl   +jumplist-perl+vertsplit
+cmdline_hist+keymap  +persistent_undo +virtualedit
+cmdline_info+lambda  +postscript  +visual
+comments+langmap +printer +visualextra
+conceal +libcall +profile +viminfo
+cryptv  +linebreak   -python  +vreplace
+cscope  +lispindent  -python3 +wildignore
+cursorbind  +listcmds+quickfix+wildmenu
+cursorshape +localmap+reltime +windows
+dialog_con_gui  -lua +rightleft   +writebackup
+diff+menu-ruby+X11
+digraphs+mksession   +scrollbind  -xfontset
+dnd +modify_fname+signs   +xim
-ebcdic  +mouse   +smartindent -xpm
+emacs_tags  +mouseshape  +startuptime +xsmp_interact
+eval+mouse_dec   +statusline  +xterm_clipboard
+ex_extra-mouse_gpm   -sun_workshop-xterm_save
+extra_search-mouse_jsbterm   +syntax  
+farsi   +mouse_netterm   +tag_binary  
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
  user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
   defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16  
-D_REENTRANT -DORBIT2=1 -pthread -I/usr/include/libgnomeui-2.0 
-I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 
-I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 
-I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 
-I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-vfs-2.0 -I/usr/lib64/gnome-vfs-2.0/include 
-I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include-g -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1  
Linking: gcc   -L/usr/local/lib -Wl,--as-needed -o vim   -lgtk-x11-2.0 
-lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 
-lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype   
-lgnomeui-2 -l

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Elimar Riesebieter

* h_east  [2016-08-23 04:49 -0700]:

> Hi Elimar,
> 
> 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter:
[...] 
> > I tried to build 7.4.2243 which failed with the above messages. So
> > why do you want to know which version I am running? This has IMHO
> > nothing to do with a compile run ;-)
> 
> No, It has to do.
> Please paste the result of `:ver` like below.

$ vim --version

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 14 2016 17:56:30)
Included patches: 1-2212
Modified by riese...@pipin.home.lxtec.de
Compiled by riese...@pipin.home.lxtec.de
Huge version with GTK3 GUI.  Features included (+) or not (-):
+acl +file_in_path+mouse_sgr   +tag_old_static
+arabic  +find_in_path-mouse_sysmouse  -tag_any_white
+autocmd +float   +mouse_urxvt +tcl
+balloon_eval+folding +mouse_xterm +termguicolors
+browse  -footer  +multi_byte  +terminfo
++builtin_terms  +fork()  +multi_lang  +termresponse
+byte_offset +gettext -mzscheme+textobjects
+channel -hangul_input+netbeans_intg   +timers
+cindent +iconv   +num64   +title
+clientserver+insert_expand   +packages+toolbar
+clipboard   +job +path_extra  +user_commands
+cmdline_compl   +jumplist+perl+vertsplit
+cmdline_hist+keymap  +persistent_undo +virtualedit
+cmdline_info+lambda  +postscript  +visual
+comments+langmap +printer +visualextra
+conceal +libcall +profile +viminfo
+cryptv  +linebreak   +python/dyn  +vreplace
+cscope  +lispindent  +python3/dyn +wildignore
+cursorbind  +listcmds+quickfix+wildmenu
+cursorshape +localmap+reltime +windows
+dialog_con_gui  +lua +rightleft   +writebackup
+diff+menu+ruby+X11
+digraphs+mksession   +scrollbind  -xfontset
+dnd +modify_fname+signs   +xim
-ebcdic  +mouse   +smartindent +xpm
+emacs_tags  +mouseshape  +startuptime +xsmp_interact
+eval+mouse_dec   +statusline  +xterm_clipboard
+ex_extra+mouse_gpm   -sun_workshop-xterm_save
+extra_search-mouse_jsbterm   +syntax  
+farsi   +mouse_netterm   +tag_binary  
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
  user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
   defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time  -g -O2 
-fdebug-prefix-map=/source/vim/vim-7.4.2212=. -fPIE -fstack-protector-strong 
-Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1  
Linking: gcc   -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic 
-Wl,-export-dynamic -Wl,-E  -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-o vim   -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject 
-lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm 
-lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lnsl  -lselinux   -lacl -lattr 
-lgpm -ldl  -L/usr/lib -llua5.2 -Wl,-E  -fstack-protector-strong 
-L/usr/local/lib  -L/usr/lib/x86_64-linux-gnu/perl/5.22/CORE -lperl -ldl -lm 
-lpthread -lcrypt   -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread 
-lieee -lm -lruby-2.3 -lpthread -lgmp -ldl -lcrypt -lm 


-- 
  Alles was viel bedacht wird ist bedenklich!;-)
 Friedrich Nietzsche

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] sh syntax script highlights multiline arrays inside an if statement incorrectly (#962)

2016-08-23 Thread cakirerkerem

DrChip wrote:
> keremc wrote:
> >
> > Inside an if statement the opening parenthesis of a multiline array
> > will not be highlighted at all, while the closing parenthesis will be
> > highlighted as an error.
> >
> >
> Hello:
> 
> Please try the attached syntax/sh.vim.
> 
> Regards,
> Chip Campbell

Hi, I've tried the attached script as well as the version on your
website but neither of them fix the issue.

Adding `shParen` to the `contains` list of `shCommandSubList` seems
to fix it but I am not very familiar with sh/vimscript so I can only
hope that it doesn't break anything.

Best,
Kerem

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Please update syntax/perl.vim

2016-08-23 Thread Bertram Scharpf

Hi,

there is a newer version of syntax/perl.vim in
. Please update the
Vim standard package to that.

Explanation:

I happened to write a Perl tutorial with lots of example
code:

v
@list = qw(foo bar baz);
print $_, "\n" for (@list);
^

As I show this during a presentation on a screen (in Vim!),
I want these pieces to be syntax highlighted. Therefore I
wrote:

syn include @Perl syntax/perl.vim
syntax region perlcourseCode matchgroup=perlcourseSep start=+^-\{64,}v$+ 
end=+^-\{64,}\^$+ contains=@Perl keepend
hi link perlcourseCode NONE
hi link perlcourseSep  MoreMsg

There is a bug in the old version of Perl syntax that makes
almost everything a function name and the whole highlighting
is spoiled.

The current version fixes this. The version shipped with Vim
is 3 years old. Please update.

Bertram



P.S.: The ftplugin reads:

function! s:PerlDemo()
  ?^-\{64,}v$?+1,/^-\{64,}\^$/y
  /^-\{64,}\^$/put
  .s/\^$/=/
  ?^-\{64,}\^$?+1,-1!perl
endfunc
command! PerlDemo  silent call s:PerlDemo()
nnoremap  :PerlDemo


-- 
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Dominique Pellé

Elimar Riesebieter  wrote:

> * h_east  [2016-08-23 04:49 -0700]:
>
>> Hi Elimar,
>>
>> 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter:
> [...]
>> > I tried to build 7.4.2243 which failed with the above messages. So
>> > why do you want to know which version I am running? This has IMHO
>> > nothing to do with a compile run ;-)
>>
>> No, It has to do.
>> Please paste the result of `:ver` like below.
>
> $ vim --version
>
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 14 2016 17:56:30)
> Included patches: 1-2212
> Modified by riese...@pipin.home.lxtec.de
> Compiled by riese...@pipin.home.lxtec.de
> Huge version with GTK3 GUI.  Features included (+) or not (-):
> +acl +file_in_path+mouse_sgr   +tag_old_static
> +arabic  +find_in_path-mouse_sysmouse  -tag_any_white
> +autocmd +float   +mouse_urxvt +tcl
> +balloon_eval+folding +mouse_xterm +termguicolors
> +browse  -footer  +multi_byte  +terminfo
> ++builtin_terms  +fork()  +multi_lang  +termresponse
> +byte_offset +gettext -mzscheme+textobjects
> +channel -hangul_input+netbeans_intg   +timers
> +cindent +iconv   +num64   +title
> +clientserver+insert_expand   +packages+toolbar
> +clipboard   +job +path_extra  +user_commands
> +cmdline_compl   +jumplist+perl+vertsplit
> +cmdline_hist+keymap  +persistent_undo +virtualedit
> +cmdline_info+lambda  +postscript  +visual
> +comments+langmap +printer +visualextra
> +conceal +libcall +profile +viminfo
> +cryptv  +linebreak   +python/dyn  +vreplace
> +cscope  +lispindent  +python3/dyn +wildignore
> +cursorbind  +listcmds+quickfix+wildmenu
> +cursorshape +localmap+reltime +windows
> +dialog_con_gui  +lua +rightleft   +writebackup
> +diff+menu+ruby+X11
> +digraphs+mksession   +scrollbind  -xfontset
> +dnd +modify_fname+signs   +xim
> -ebcdic  +mouse   +smartindent +xpm
> +emacs_tags  +mouseshape  +startuptime +xsmp_interact
> +eval+mouse_dec   +statusline  +xterm_clipboard
> +ex_extra+mouse_gpm   -sun_workshop-xterm_save
> +extra_search-mouse_jsbterm   +syntax
> +farsi   +mouse_netterm   +tag_binary
>system vimrc file: "$VIM/vimrc"
>  user vimrc file: "$HOME/.vimrc"
>  2nd user vimrc file: "~/.vim/vimrc"
>   user exrc file: "$HOME/.exrc"
>   system gvimrc file: "$VIM/gvimrc"
> user gvimrc file: "$HOME/.gvimrc"
> 2nd user gvimrc file: "~/.vim/gvimrc"
>defaults file: "$VIMRUNTIME/defaults.vim"
> system menu file: "$VIMRUNTIME/menu.vim"
>   fall-back for $VIM: "/usr/share/vim"
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread 
> -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -Wdate-time  -g -O2 -fdebug-prefix-map=/source/vim/vim-7.4.2212=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=1
> Linking: gcc   -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic 
> -Wl,-export-dynamic -Wl,-E  -fPIE -pie -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o vim   -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 
> -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 
> -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lnsl  
> -lselinux   -lacl -lattr -lgpm -ldl  -L/usr/lib -llua5.2 -Wl,-E  
> -fstack-protector-strong -L/usr/local/lib  
> -L/usr/lib/x86_64-linux-gnu/perl/5.22/CORE -lperl -ldl -lm -lpthread -lcrypt  
>  -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lieee -lm 
> -lruby-2.3 -lpthread -lgmp -ldl -lcrypt -lm



The title of the email thread says:
"Build 7.4.2243: Makefile:41: recipe for target 'report' failed"

Yet the above output of  :ver  says
Included patches: 1-2212

So is the tile wrong? or is the output of :ver done on a different Vim?

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 because you are subscribed to the Google Groups 
"vim_dev" group.

Re: Please update syntax/perl.vim

2016-08-23 Thread Christian Brabandt


Am 2016-08-23 14:49, schrieb Bertram Scharpf:

Hi,

there is a newer version of syntax/perl.vim in
. Please update the
Vim standard package to that.

Explanation:

I happened to write a Perl tutorial with lots of example
code:

v
@list = qw(foo bar baz);
print $_, "\n" for (@list);
^

As I show this during a presentation on a screen (in Vim!),
I want these pieces to be syntax highlighted. Therefore I
wrote:

syn include @Perl syntax/perl.vim
syntax region perlcourseCode matchgroup=perlcourseSep
start=+^-\{64,}v$+ end=+^-\{64,}\^$+ contains=@Perl keepend
hi link perlcourseCode NONE
hi link perlcourseSep  MoreMsg

There is a bug in the old version of Perl syntax that makes
almost everything a function name and the whole highlighting
is spoiled.

The current version fixes this. The version shipped with Vim
is 3 years old. Please update.

Bertram


Open an issue at the upstream vim-perl repository
to send an updated syntax file for inclusion with Vim to Bram.

There is nothing we can do here.

PS: There already exists https://github.com/vim-perl/vim-perl/issues/197
doesn't look like upstream is eager to update its syntax files 
regularly.


Best,
Christian

--
--
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 Groups "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Please update syntax/perl.vim

2016-08-23 Thread Bertram Scharpf

On Tuesday, 23. Aug 2016, 15:05:53 +0200, Christian Brabandt wrote:
> Am 2016-08-23 14:49, schrieb Bertram Scharpf:
> > there is a newer version of syntax/perl.vim in
> > . Please update the
> > Vim standard package to that.
> 
> Open an issue at the upstream vim-perl repository
> to send an updated syntax file for inclusion with Vim to Bram.
> 
> There is nothing we can do here.
> 
> PS: There already exists https://github.com/vim-perl/vim-perl/issues/197
> doesn't look like upstream is eager to update its syntax files 
> regularly.

This is about syntax/perl6.vim (six). Further, they
recommend to write to vim-dev.

So I will tweak my package build tree. Sorry for the noise.
I will not report a bug again.

Bertram


-- 
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Please update syntax/perl.vim

2016-08-23 Thread Christian Brabandt

Hi Bertram!

On Di, 23 Aug 2016, Bertram Scharpf wrote:

> On Tuesday, 23. Aug 2016, 15:05:53 +0200, Christian Brabandt wrote:
> > Am 2016-08-23 14:49, schrieb Bertram Scharpf:
> > > there is a newer version of syntax/perl.vim in
> > > . Please update the
> > > Vim standard package to that.
> > 
> > Open an issue at the upstream vim-perl repository
> > to send an updated syntax file for inclusion with Vim to Bram.
> > 
> > There is nothing we can do here.
> > 
> > PS: There already exists https://github.com/vim-perl/vim-perl/issues/197
> > doesn't look like upstream is eager to update its syntax files 
> > regularly.
> 
> This is about syntax/perl6.vim (six).

I know. That's why it was a post scriptum

> Further, they recommend to write to vim-dev.

That is not how runtime files are distributed. Maintainers are expected 
to send updated files to Bram for inclusion. We generally don't go 
hunting for files all over the internet to include with Vim, because

1) we don't know if we are allowed to do so
2) we don't know if the files are stable enough to be distributed with
   Vim
3) we don't know if the file is actively maintained.

> So I will tweak my package build tree. Sorry for the noise.
> I will not report a bug again.

Sorry for that. But as explained, it is clearly a problem that can only 
be solved by the runtime file maintainer.

Best,
Christian
-- 
Man kann seiner eigenen Zeit nicht böse sein, ohne selbst Schaden zu
nehmen.
-- Robert Musil

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Elimar Riesebieter

* Dominique Pellé  [2016-08-23 14:53 +0200]:

[...]
> >> 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter:
> > [...]
> >> > I tried to build 7.4.2243 which failed with the above messages. So
> >> > why do you want to know which version I am running? This has IMHO
> >> > nothing to do with a compile run ;-)
[...] 
> The title of the email thread says:
> "Build 7.4.2243: Makefile:41: recipe for target 'report' failed"

Should say "Built 7.4.2243" ?

> Yet the above output of  :ver  says
> Included patches: 1-2212
> 
> So is the tile wrong? or is the output of :ver done on a different Vim?

As mentioned above:

I tried to build 7.4.2243 which failed.

Sigh
Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: compiler warning w/ Studio & gtk3 GUI

2016-08-23 Thread Danek Duvall

On Tue, Aug 23, 2016 at 06:01:54PM +0900, Kazunobu Kuriyama wrote:

> Hi Danek,
> 
> I think that mismatch is not our fault, either.

Yeah, that was my thought, but I thought perhaps the Solaris setup was
somehow incorrect.  But it really does look like a bug in glib/gtk.  I'll
see if I can get a bug filed upstream.

> That said, it would take some time to file the issue against them and wait
> for their response to that; it would be better for us to do something about
> that for ourselves.
> 
> So I made a patch for fixing the issue, which is attached to this mail.
> 
> For that, I assumed that the Solaris Studio had the predefined constant
> macro __SUNPRO_C.  Is that assumption OK?

Yup, that seems reasonable.  And the patch works just fine -- no more
warnings, and the result seems to work just fine.

> If that's OK, could you try the patch to check if it works as expected?
> 
> Note that the patch includes some minor fixes on coding style, too.
> 
> 
> > glib is 2.46, gtk3 is 3.18.
> >
> > I don't see this in the travis logs, but I can't tell from there what
> > versions of glib and gtk are in use.
> >
> > Does this look familiar to anyone?
> 
> I didn't see either clang or gcc (generic one, not the one which is a
> symbolic link to clang) giving me any warning on the mismatch.  I didn't
> know about that until I read you report.

Yeah; I wonder if gcc would show that with some more -W flags thrown in
there.  I guess I'm a bit surprised that clang didn't show it; I thought it
did a better job of finding bad code.  I guess that's why we try to have a
diverse bundle of compilers.  :)

Thanks,
Danek

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 8 pre-announcement

2016-08-23 Thread skywind3000

Bram:

> Work on Vim 8.0 is coming close to an end.  I hope version 8.0 can be
> released in about two weeks.
> 
> This is a last chance to modify new features in a way that is not
> backwards compatible.  Once 8.0 is out we can't make changes that would
> break plugins.
> 


Visual C++ 6 can play a sound when build stop.

so Can I have a command ':bell' to ring the bell to notify myself that my 
async-build job has finished and I should check the quickfix output now while I 
am focusing on editing or navigating source.



-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 8 pre-announcement

2016-08-23 Thread skywind3000

> Bram:
> 
> > Work on Vim 8.0 is coming close to an end.  I hope version 8.0 can be
> > released in about two weeks.
> > 
> > This is a last chance to modify new features in a way that is not
> > backwards compatible.  Once 8.0 is out we can't make changes that would
> > break plugins.
> > 
> 
> 
> Visual C++ 6 can play a sound when build stop.
> 
> so Can I have a command ':bell' to ring the bell to notify myself that my 
> async-build job has finished and I should check the quickfix output now while 
> I am focusing on editing or navigating source.

afplay or other command line utilities could be used to play a .wav file in the 
desktop gvim, but there is no way to make a voice in a terminal vim.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 8 pre-announcement

2016-08-23 Thread Christian Brabandt

Hi skywind3000!

On Di, 23 Aug 2016, skywind3000 wrote:

> so Can I have a command ':bell' to ring the bell to notify myself that my 
> async-build job has finished and I should check the quickfix output now while 
> I am focusing on editing or navigating source.

You mean like
:com Bell exe "norm! \"
or
:com! Bell :sil! !printf "\a"

of course you can also use mplayer or some other console command to play 
something (preferably in the background)


Best,
Christian
-- 
Manche Menschen sind wie ein offenes Buch: lauter leere Seiten.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 8 pre-announcement

2016-08-23 Thread skywind3000

Christian: 
> Hi skywind3000!
> 
> On Di, 23 Aug 2016, skywind3000 wrote:
> 
> > so Can I have a command ':bell' to ring the bell to notify myself that my 
> > async-build job has finished and I should check the quickfix output now 
> > while I am focusing on editing or navigating source.
> 
> You mean like
> :com Bell exe "norm! \"

very tricky !!
That's what I need 

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

(bug) :sil!, :try and :echoerr

2016-08-23 Thread 'Andy Wokula' via vim_dev


gVim 7.4.2239

:sil! throw 'foo'
" throws exception (ok)
" :h :sil  only talks about error messages, not exceptions

:sil! try|echoerr 'foo'|endtry
" nothing, should probably throw an exception, given
" error message is turned into an exception according to :h :echoerr
" worse: this command confuses Vim

:sil! throw 'foo'
" nothing (bug)

--
Andy

--
--
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 Groups "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Does the visual bell work in GTK+ 3?

2016-08-23 Thread Tony Mechelynck

With the following settings:

:verbose set eb? vb? bo? t_vb?
  errorbells
Last set from ~/.vimrc
  visualbell
Last set from ~/.vimrc
belloff=
t_vb=^[|1000f
Last set from ~/.vimrc

(the latter is set in a GUIEnter autocommand, the rest in the .vimrc
mainline code)

when I hit  repeatedly, I hear no sound and I see no visual bell.
This is for gvim 7.4.2243 with GTK3 GUI.

With the visual bell time set at a full second, it ought not to be too
fast for me to see it, don't you think? I have tested other values,
including the default, with the same result, or lack of one; and I
know about |option-backslash| to enter the vertical bar into the
option value.


Best regards,
Tony.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Dominique Pellé

Elimar Riesebieter  wrote:

> * Dominique Pellé  [2016-08-23 14:53 +0200]:
>
> [...]
>> >> 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter:
>> > [...]
>> >> > I tried to build 7.4.2243 which failed with the above messages. So
>> >> > why do you want to know which version I am running? This has IMHO
>> >> > nothing to do with a compile run ;-)
> [...]
>> The title of the email thread says:
>> "Build 7.4.2243: Makefile:41: recipe for target 'report' failed"
>
> Should say "Built 7.4.2243" ?
>
>> Yet the above output of  :ver  says
>> Included patches: 1-2212
>>
>> So is the tile wrong? or is the output of :ver done on a different Vim?
>
> As mentioned above:
>
> I tried to build 7.4.2243 which failed.
>
> Sigh
> Elimar

The error message you gave in the original message was not a
build error (i.e not a compilation error), but a test failure. Presumably
you built vim-7.4.2243 successfully, ran the tests and they failed,
somehow.

Test_tabpage_with_tab_modifier() that failed was introduced
recently in vim-7.4.2237, but I don't know why it failed.
I can't reproduce it.

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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

2016-08-23 Thread Elimar Riesebieter

* Dominique Pellé  [2016-08-23 21:58 +0200]:

> Elimar Riesebieter  wrote:
> 
> > * Dominique Pellé  [2016-08-23 14:53 +0200]:
> >
> > [...]
> >> >> 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter:
> >> > [...]
> >> >> > I tried to build 7.4.2243 which failed with the above messages. So
> >> >> > why do you want to know which version I am running? This has IMHO
> >> >> > nothing to do with a compile run ;-)
> > [...]
> >> The title of the email thread says:
> >> "Build 7.4.2243: Makefile:41: recipe for target 'report' failed"
> >
> > Should say "Built 7.4.2243" ?
> >
> >> Yet the above output of  :ver  says
> >> Included patches: 1-2212
> >>
> >> So is the tile wrong? or is the output of :ver done on a different Vim?
> >
> > As mentioned above:
> >
> > I tried to build 7.4.2243 which failed.
> >
> > Sigh
> > Elimar
> 
> The error message you gave in the original message was not a
> build error (i.e not a compilation error), but a test failure. Presumably
> you built vim-7.4.2243 successfully, ran the tests and they failed,
> somehow.
> 
> Test_tabpage_with_tab_modifier() that failed was introduced
> recently in vim-7.4.2237, but I don't know why it failed.
> I can't reproduce it.

Thanks for clarifying. Ill investigate further.

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Patch 7.4.2244

2016-08-23 Thread Bram Moolenaar


Patch 7.4.2244
Problem:Adding pattern to ":oldfiles" is not a generic solution.
Solution:   Add the ":filter /pat/ cmd" command modifier.  Only works for some
commands right now.
Files:  src/structs.h, src/ex_docmd.c, src/ex_cmds.h, src/message.c,
src/proto/message.pro, runtime/doc/starting.txt,
runtime/doc/various.txt, src/testdir/test_viminfo.vim,
src/testdir/test_alot.vim, src/testdir/test_filter_cmd.vim,
src/Makefile


*** ../vim-7.4.2243/src/structs.h   2016-08-22 23:04:29.206161702 +0200
--- src/structs.h   2016-08-23 22:01:52.378554550 +0200
***
*** 571,576 
--- 571,577 
  # ifdef FEAT_AUTOCMD
  char_u*save_ei;   /* saved value of 'eventignore' */
  # endif
+ regmatch_Tfilter_regmatch;/* set by :filter /pat/ */
  } cmdmod_T;
  
  #define MF_SEED_LEN   8
*** ../vim-7.4.2243/src/ex_docmd.c  2016-08-21 19:07:14.261008144 +0200
--- src/ex_docmd.c  2016-08-23 22:33:12.762029931 +0200
***
*** 1781,1786 
--- 1781,1787 
  linenr_T  lnum;
  long  n;
  char_u*errormsg = NULL;   /* error message */
+ char_u*after_modifier = NULL;
  exarg_T   ea; /* Ex command arguments */
  long  verbose_save = -1;
  int   save_msg_scroll = msg_scroll;
***
*** 1917,1922 
--- 1918,1941 
cmdmod.keepjumps = TRUE;
continue;
  
+   case 'f':   /* only accept ":filter {pat} cmd" */
+   {
+   char_u *reg_pat;
+ 
+   if (!checkforcmd(&p, "filter", 4)
+   || *p == NUL || ends_excmd(*p))
+   break;
+   p = skip_vimgrep_pat(p, ®_pat, NULL);
+   if (p == NULL || *p == NUL)
+   break;
+   cmdmod.filter_regmatch.regprog =
+   vim_regcomp(reg_pat, RE_MAGIC);
+   if (cmdmod.filter_regmatch.regprog == NULL)
+   break;
+   ea.cmd = p;
+   continue;
+   }
+ 
/* ":hide" and ":hide | cmd" are not modifiers */
case 'h':   if (p != ea.cmd || !checkforcmd(&p, "hide", 3)
   || *p == NUL || ends_excmd(*p))
***
*** 2041,2046 
--- 2060,2066 
}
break;
  }
+ after_modifier = ea.cmd;
  
  #ifdef FEAT_EVAL
  ea.skip = did_emsg || got_int || did_throw || (cstack->cs_idx >= 0
***
*** 2374,2380 
{
STRCPY(IObuff, _("E492: Not an editor command"));
if (!sourcing)
!   append_command(*cmdlinep);
errormsg = IObuff;
did_emsg_syntax = TRUE;
}
--- 2394,2407 
{
STRCPY(IObuff, _("E492: Not an editor command"));
if (!sourcing)
!   {
!   /* If the modifier was parsed OK the error must be in the
!* following command */
!   if (after_modifier != NULL)
!   append_command(after_modifier);
!   else
!   append_command(*cmdlinep);
!   }
errormsg = IObuff;
did_emsg_syntax = TRUE;
}
***
*** 2818,2823 
--- 2845,2851 
case CMD_echomsg:
case CMD_echon:
case CMD_execute:
+   case CMD_filter:
case CMD_help:
case CMD_hide:
case CMD_ijump:
***
*** 2989,2994 
--- 3017,3024 
free_string_option(cmdmod.save_ei);
  }
  #endif
+ if (cmdmod.filter_regmatch.regprog != NULL)
+   vim_regfree(cmdmod.filter_regmatch.regprog);
  
  cmdmod = save_cmdmod;
  
***
*** 3323,3328 
--- 3353,3359 
  {"botright", 2, FALSE},
  {"browse", 3, FALSE},
  {"confirm", 4, FALSE},
+ {"filter", 4, FALSE},
  {"hide", 3, FALSE},
  {"keepalt", 5, FALSE},
  {"keepjumps", 5, FALSE},
***
*** 3833,3838 
--- 3864,3870 
case CMD_cfdo:
case CMD_confirm:
case CMD_debug:
+   case CMD_filter:
case CMD_folddoclosed:
case CMD_folddoopen:
case CMD_hide:
*** ../vim-7.4.2243/src/ex_cmds.h   2016-08-20 18:36:48.296969153 +0200
--- src/ex_cmds.h   2016-08-23 22:52:33.835678370 +0200
***
*** 544,549 
--- 544,552 
  EX(CMD_filetype,  "filetype", ex_filetype,
EXTRA|TRLBAR|CMDWIN,
ADDR_LINES),
+ EX(CMD_filter,"filter",   ex_wrongmodifie

Patch 7.4.2245

2016-08-23 Thread Bram Moolenaar


Patch 7.4.2245 (after 7.4.2244)
Problem:Filter test fails.
Solution:   Include missing changes.
Files:  src/buffer.c


*** ../vim-7.4.2244/src/buffer.c2016-08-20 15:05:35.554703213 +0200
--- src/buffer.c2016-08-23 23:10:23.598122051 +0200
***
*** 2931,2942 
|| (vim_strchr(eap->arg, '#')
  && (buf == curbuf || curwin->w_alt_fnum != buf->b_fnum)))
continue;
-   msg_putchar('\n');
if (buf_spname(buf) != NULL)
vim_strncpy(NameBuff, buf_spname(buf), MAXPATHL - 1);
else
home_replace(buf, buf->b_fname, NameBuff, MAXPATHL, TRUE);
  
len = vim_snprintf((char *)IObuff, IOSIZE - 20, "%3d%c%c%c%c%c \"%s\"",
buf->b_fnum,
buf->b_p_bl ? ' ' : 'u',
--- 2931,2944 
|| (vim_strchr(eap->arg, '#')
  && (buf == curbuf || curwin->w_alt_fnum != buf->b_fnum)))
continue;
if (buf_spname(buf) != NULL)
vim_strncpy(NameBuff, buf_spname(buf), MAXPATHL - 1);
else
home_replace(buf, buf->b_fname, NameBuff, MAXPATHL, TRUE);
+   if (message_filtered(NameBuff))
+   continue;
  
+   msg_putchar('\n');
len = vim_snprintf((char *)IObuff, IOSIZE - 20, "%3d%c%c%c%c%c \"%s\"",
buf->b_fnum,
buf->b_p_bl ? ' ' : 'u',
*** ../vim-7.4.2244/src/version.c   2016-08-23 23:50:06.872279942 +0200
--- src/version.c   2016-08-24 00:11:37.144463503 +0200
***
*** 765,766 
--- 765,768 
  {   /* Add new patch number below this line */
+ /**/
+ 2245,
  /**/

-- 
hundred-and-one symptoms of being an internet addict:
57. You begin to wonder how on earth your service provider is allowed to call
200 hours per month "unlimited."

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ftp.vim.org down?

2016-08-23 Thread Bram Moolenaar


I wrote:

> Elimar Riesebieter wrote:
> 
> > ping ftp.vim.org
> > 
> > PING ftp.vim.org(ftp.nluug.nl (2001:67c:6ec:221:145:220:21:40)) 56 data 
> > bytes
> > 
> > --- ftp.vim.org ping statistics ---
> > 3 packets transmitted, 0 received, 100% packet loss, time 2025ms
> 
> Yes, it's broken.  Unknown when it will be repaired.

Aaaand, it's back!

-- 
Creating the world with Emacs:   M-x let-there-be-light
Creating the world with Vim: :make world

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Link failure in Tiny build 7.4.2245

2016-08-23 Thread Tony Mechelynck

Huge build proceeds normally to completion.

In 7.4.2245 Tiny build:

link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly.
  gcc   -L/usr/local/lib -Wl,--as-needed-o vi objects/arabic.o
objects/buffer.o objects/blowfish.o objects/charset.o objects/crypt.o
objects/crypt_zip.o objects/dict.o objects/diff.o objects/digraph.o
objects/edit.o objects/eval.o objects/evalfunc.o objects/ex_cmds.o
objects/ex_cmds2.o objects/ex_docmd.o objects/ex_eval.o
objects/ex_getln.o objects/farsi.o objects/fileio.o objects/fold.o
objects/getchar.o objects/hardcopy.o objects/hashtab.o
objects/if_cscope.o objects/if_xcmdsrv.o objects/list.o objects/mark.o
objects/memline.o objects/menu.o objects/misc1.o objects/misc2.o
objects/move.o objects/mbyte.o objects/normal.o objects/ops.o
objects/option.o objects/os_unix.o objects/pathdef.o
objects/popupmnu.o objects/quickfix.o objects/regexp.o
objects/screen.o objects/search.o objects/sha256.o objects/spell.o
objects/spellfile.o objects/syntax.o objects/tag.o objects/term.o
objects/ui.o objects/undo.o objects/userfunc.o objects/version.o
objects/window.o  objects/json.o objects/main.o
objects/memfile.o objects/message.o-lSM -lICE -lXpm -lXt -lX11
-lXdmcp -lSM -lICE  -lm -ltinfo  -lgpm -ldl
objects/ex_docmd.o: In function `do_one_cmd':
ex_docmd.c:(.text+0x4757): undefined reference to `skip_vimgrep_pat'
collect2: error: ld returned 1 exit status
link.sh: Linking failed
Makefile:1856: recipe for target 'vi' failed
make: *** [vi] Error 1
exit status 2


Best regards,
Tony.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 7.4.2244

2016-08-23 Thread Bram Moolenaar


I wrote:

> Patch 7.4.2244
> Problem:Adding pattern to ":oldfiles" is not a generic solution.
> Solution:   Add the ":filter /pat/ cmd" command modifier.  Only works for some
> commands right now.
> Files:  src/structs.h, src/ex_docmd.c, src/ex_cmds.h, src/message.c,
> src/proto/message.pro, runtime/doc/starting.txt,
> runtime/doc/various.txt, src/testdir/test_viminfo.vim,
> src/testdir/test_alot.vim, src/testdir/test_filter_cmd.vim,
> src/Makefile

Note that this is incomplete.  Many commands output messages not as
whole lines but pieces at a time.  This requires filtering in many
places.  Or perhaps buffering the output until a line is complete.
Both are not so easy.

I do think that this method of filtering is better, since adding the
pattern after the command doesn't work for commands that already take an
argument.

-- 
hundred-and-one symptoms of being an internet addict:
59. Your wife says communication is important in a marriage...so you buy
another computer and install a second phone line so the two of you can
chat.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Patch 7.4.2246

2016-08-23 Thread Bram Moolenaar


Patch 7.4.2246 (after 7.4.2244)
Problem:Oldfiles test fails.
Solution:   Include missing changes.
Files:  src/ex_cmds.c


*** ../vim-7.4.2245/src/ex_cmds.c   2016-08-21 22:39:30.995567145 +0200
--- src/ex_cmds.c   2016-08-23 23:03:10.013990452 +0200
***
*** 8456,8489 
  list_T*l = get_vim_var_list(VV_OLDFILES);
  listitem_T*li;
  int   nr = 0;
- char_u*reg_pat = NULL;
  char_u*fname;
- regmatch_Tregmatch;
  
  if (l == NULL)
msg((char_u *)_("No old files"));
  else
  {
-   if (*eap->arg != NUL)
-   {
-   if (skip_vimgrep_pat(eap->arg, ®_pat, NULL) == NULL)
-   {
-   EMSG(_(e_invalpat));
-   return;
-   }
-   regmatch.regprog = vim_regcomp(reg_pat, p_magic ? RE_MAGIC : 0);
-   if (regmatch.regprog == NULL)
-   return;
-   }
- 
msg_start();
msg_scroll = TRUE;
for (li = l->lv_first; li != NULL && !got_int; li = li->li_next)
{
++nr;
fname = get_tv_string(&li->li_tv);
!   if (reg_pat == NULL || *reg_pat == NUL
! || vim_regexec(®match, fname, (colnr_T)0))
{
msg_outnum((long)nr);
MSG_PUTS(": ");
--- 8456,8474 
  list_T*l = get_vim_var_list(VV_OLDFILES);
  listitem_T*li;
  int   nr = 0;
  char_u*fname;
  
  if (l == NULL)
msg((char_u *)_("No old files"));
  else
  {
msg_start();
msg_scroll = TRUE;
for (li = l->lv_first; li != NULL && !got_int; li = li->li_next)
{
++nr;
fname = get_tv_string(&li->li_tv);
!   if (!message_filtered(fname))
{
msg_outnum((long)nr);
MSG_PUTS(": ");
***
*** 8493,8500 
ui_breakcheck();
}
}
-   if (*eap->arg != NUL)
-   vim_regfree(regmatch.regprog);
  
/* Assume "got_int" was set to truncate the listing. */
got_int = FALSE;
--- 8478,8483 
*** ../vim-7.4.2245/src/version.c   2016-08-24 00:12:08.868171000 +0200
--- src/version.c   2016-08-24 00:30:06.150472899 +0200
***
*** 765,766 
--- 765,768 
  {   /* Add new patch number below this line */
+ /**/
+ 2246,
  /**/


-- 
Q: Should I clean my house or work on Vim?
A: Whatever contains more bugs.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Patch 7.4.2247

2016-08-23 Thread Bram Moolenaar


Patch 7.4.2247 (after 7.4.2244)
Problem:Tiny build fails. (Tony Mechelynck)
Solution:   Remove #ifdef.
Files:  src/ex_cmds.c


*** ../vim-7.4.2246/src/ex_cmds.c   2016-08-24 00:30:49.470083766 +0200
--- src/ex_cmds.c   2016-08-24 00:37:37.990413268 +0200
***
*** 8392,8398 
  }
  #endif
  
- #if defined(FEAT_QUICKFIX) || defined(FEAT_EVAL) || defined(PROTO)
  /*
   * Skip over the pattern argument of ":vimgrep /pat/[g][j]".
   * Put the start of the pattern in "*s", unless "s" is NULL.
--- 8392,8397 
***
*** 8444,8450 
  }
  return p;
  }
- #endif
  
  #if defined(FEAT_EVAL) || defined(PROTO)
  /*
--- 8443,8448 
*** ../vim-7.4.2246/src/version.c   2016-08-24 00:30:49.474083730 +0200
--- src/version.c   2016-08-24 00:38:27.485968458 +0200
***
*** 765,766 
--- 765,768 
  {   /* Add new patch number below this line */
+ /**/
+ 2247,
  /**/

-- 
I'm trying to be an optimist, but I don't think it'll work.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bug][patch] Unexpectedly preview window opened, after the `:ptjump` command canceled.

2016-08-23 Thread h_east

Hi Bram and developers,

How to reproduce:
- Change directory to your local vim/src directory.
  $ cd /path-to-your-vim-clone-dir/vim/src
- Start vanilla Vim.
  $ ./vim -Nu NONE
- Do tagjump and display in the preview window. (In fact, it becomes selected 
wait because candidates are two)
  :ptjump cmdmod
- Cancel the selection.
  
- Display the help.
  :help

Expected behavior:
- Open the help window and display the help document.

Actual behavior:
- Two windows opened.
  Top window is preview window, and displayed the help document.
  Next one is empty window.


An attached patch fix this.
Sorry for without a test.
Tell me if there is an easy way to test in the Vim script.

--
Best regards,
Hirohito Higashi (a.k.a. h_east)

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/tag.c b/src/tag.c
index e388a43..a198a31 100644
--- a/src/tag.c
+++ b/src/tag.c
@@ -1078,6 +1078,9 @@ end_do_tag:
 	curwin->w_tagstackidx = tagstackidx;
 #ifdef FEAT_WINDOWS
 postponed_split = 0;	/* don't split next time */
+# ifdef FEAT_QUICKFIX
+g_do_tagpreview = 0;	/* don't preview next time */
+# endif
 #endif
 
 #ifdef FEAT_CSCOPE

Re: Patch 7.4.2231

2016-08-23 Thread Christian Brabandt


Am 2016-08-22 20:29, schrieb Bram Moolenaar:
Perhaps we better add a generic way to filter the output.  
Unfortunately

we can't use "command | grep /pattern/".  Not all commands accept
another command following.


True, but this is already documented at :h :bar and the obvious 
workaround

for that case would be to use :exe 'cmd' | grep /pattern/


We could put it in front:

filter /pattern/ command

It's like a command modifier then.  But one with an argument.
Note that the filtering would happen line-by-line, thus if there is an
item that takes several lines only matching ones would show up.


I am sorry, but this is ugly.

Best,
Christian

--
--
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 Groups "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

tuxproject builds

Re: compiler warning w/ Studio & gtk3 GUI

Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: [vim/vim] termguicolors doesn't work in terminal Vim (#993)

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: [patch] :make doesn't support encoding conversion

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: [vim/vim] sh syntax script highlights multiline arrays inside an if statement incorrectly (#962)

Please update syntax/perl.vim

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: Please update syntax/perl.vim

Re: Please update syntax/perl.vim

Re: Please update syntax/perl.vim

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: compiler warning w/ Studio & gtk3 GUI

Re: Vim 8 pre-announcement

Re: Vim 8 pre-announcement

Re: Vim 8 pre-announcement

Re: Vim 8 pre-announcement

(bug) :sil!, :try and :echoerr

Does the visual bell work in GTK+ 3?

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Patch 7.4.2244

Patch 7.4.2245

Re: ftp.vim.org down?

Link failure in Tiny build 7.4.2245

Re: Patch 7.4.2244

Patch 7.4.2246

Patch 7.4.2247

[bug][patch] Unexpectedly preview window opened, after the `:ptjump` command canceled.

Re: Patch 7.4.2231

34 matches

Site Navigation

Mail list logo

Footer information