On 1 August 2012 04:38, Kana Natsuno <whileimautomaton@...> wrote:
> On Wednesday, August 1, 2012 7:03:48 AM UTC+9, Lech Lorens wrote:
>> From ":help InsertLeave":
>>
>>                                                       *InsertLeave*
>> InsertLeave                   When leaving Insert mode.  Also when using
>>                               CTRL-O |i_CTRL-O|.  But not for |i_CTRL-C|.
>
> I've also confirmed the problem.
> <C-c> usually does not trigger InsertLeave as documented,
> but <C-c> triggers InsertLeave after adding a key mapping as Mikey described.

Whoops, seems that I have some serious problems with reading
comprehension. I misunderstood what the issue was, sorry.

Cheers,
Lech

--
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

On 29/07/12 11:41 PM, Balazs Kezes wrote:
> My vim seems to flicker on big terminals because the output buffer is
> limited to 2K. Outputting a full redraw of large screen needs much more
> characters (especially if it has lots of colors). Currently it is
> distributed to several writes (separated by several milliseconds on my
> slow machine). This causes that when I press Page Down for example I can
> see the black flicker in bottom part of the terminal.
>
> I propose increasing this buffer to 64K. So in src/term.c:
> -#  define OUT_SIZE 2047
> +#  define OUT_SIZE 65535

This sounds like a good idea to me.

Ben.



--
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

Sorry for top post. And sorry, I'm talking about this without making
sure the behavour.
I wonder why you are trying to get InsertLeave with nnoremap. I
beleave that leader <c-c> afect to insert mode at the first. So I'm
thinking it should be inoremap to do that.


On 8/1/12, Mikey <smieciarski@...> wrote:
> Using <C-c> as a leader key breaks 'Does not trigger the InsertLeave
> autocommand event'
>
> I use GVim 7.3.600.
> Steps to reproduce:
>
> gvim -u NONE -U NONE
> set nocompatible
> au InsertLeave * :echo "InsertLeave event triggered"
> nnoremap <C-c>a k
>
> Now enter some text and while being in insert mode press <C-c> to exit
> to normal mode.
>
> --
> 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
>


--
- Yasuhiro Matsumoto

--
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

On Wednesday, August 1, 2012 10:25:57 AM UTC-5, mattn wrote:
> Sorry for top post. And sorry, I'm talking about this without making
>
> sure the behavour.
>
> I wonder why you are trying to get InsertLeave with nnoremap. I
>
> beleave that leader <c-c> afect to insert mode at the first. So I'm
>
> thinking it should be inoremap to do that.
>
>

I think the problem is that the OP DOESN'T want the InsertLeave autocmd to fire,
so he uses <C-C> to exit insert mode. The docs say <C-C> should exit insert mode
without firing the autocmd. If I understand correctly, with <C-C> as part of the
LHS of a *normal mode* mapping, exiting Insert mode with <C-C> DOES trigger the
autocmd.

I also confirm this behavior. I would expect that a <C-C> mapping in normal mode
has no effect on behavior of insert mode, but in this case, it does.

--
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

On Aug 1, 5:37 pm, Ben Fritz <fritzophre...@...> wrote:
> I think the problem is that the OP DOESN'T want the InsertLeave autocmd to
fire, so he uses <C-C> to exit insert mode. The docs say <C-C> should exit
insert mode without firing the autocmd. If I understand correctly, with <C-C> as
part of the LHS of a *normal mode* mapping, exiting Insert mode with <C-C> DOES
trigger the autocmd.

That's exactly what I meant.

--
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

Hi

Attached patch updates the Breton spelling dictionary.

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

Hi,

2012/07/22 4:01:04 UTC+9 Ingo Karkat:
> I like the different highlighting of added / changed / removed. Having a
>
> different group for the file name is probably less important, but would be
easy
>
> to add, too.

I don't think it is important, but if you send me a pull request, I will include
it.

> One more request, though: Wouldn't it be more appropriate to name the syntax
>
> "hgcommit", because it's more precise, and for future compatibility?

OK, I changed the name from "hg" to "hgcommit".
A patch for filetype.vim was also updated.
https://gist.github.com/3129572
(https://github.com/k-takata/hg-vim)


Bram,
I think it is now ready for inclusion.
I hope this would be a help for hg users and also for Vim contributors.

Thank you.
--
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

Ben Schmidt wrote:

> On 29/07/12 11:41 PM, Balazs Kezes wrote:
> > My vim seems to flicker on big terminals because the output buffer is
> > limited to 2K. Outputting a full redraw of large screen needs much more
> > characters (especially if it has lots of colors). Currently it is
> > distributed to several writes (separated by several milliseconds on my
> > slow machine). This causes that when I press Page Down for example I can
> > see the black flicker in bottom part of the terminal.
> >
> > I propose increasing this buffer to 64K. So in src/term.c:
> > -#  define OUT_SIZE 2047
> > +#  define OUT_SIZE 65535
>
> This sounds like a good idea to me.

The purpose of the output buffer is not to avoid flicker.  It's to avoid
many small updates, which is slow.

Computers have much more memory now, thus we could make the buffer
bigger.  But they are also much faster, thus the need for reducing the
number of calls is smaller.  I suppose making it 8K would be OK.

I'm mainly worried about slow remote connections.  Personally that's
where I sometimes have problems (ssh over GPRS).  I'm not sure what the
relation is between the buffer size and responsiveness.  While typing
out_flush() should be called quite often.


--
% cat /usr/include/sys/errno.h
#define EPERM  1  /* Operation not permitted */
#define ENOENT  2  /* No such file or directory */
#define ESRCH  3  /* No such process */
[...]
#define EMACS  666  /* Too many macros */
%

  /// Bram Moolenaar -- Bram@... -- 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

Yasuhiro Matsumoto wrote:

> on windows, gvim become slow while executing shell. When type alt-tab
> to switch focus of windows, vim don't work quickly. If it have many
> window messages, I guess, vim should do first priority.
>
> https://gist.github.com/3212747
>
> diff -r 0fc0108517a8 src/os_win32.c
> --- a/src/os_win32.c Sun Jul 29 12:55:32 2012 +0200
> +++ b/src/os_win32.c Tue Jul 31 11:06:26 2012 +0900
> @@ -3319,8 +3319,7 @@
>  	    {
>  	 TranslateMessage(&msg);
>  	 pDispatchMessage(&msg);
> -     }
> -     if (WaitForSingleObject(pi.hProcess, delay) != WAIT_TIMEOUT)
> +     } else if (WaitForSingleObject(pi.hProcess, delay) != WAIT_TIMEOUT)
>  	 break;
>
>  	    /* We start waiting for a very short time and then increase it, so

Good idea.  This still increases the delay after each processed message.
We can use "continue" to avoid that.  And we could also reset the delay.

I'll make a patch that does this, please try it out and see if it can be
improved.

--
Some of the well know MS-Windows errors:
	 EHUH  Unexpected error
	 EUSER  User error, not our fault!
	 EGOD  Horrible problem, god knows what has happened
	 EERR  Errornous error: nothing wrong

  /// Bram Moolenaar -- Bram@... -- 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

Dominique Pelle wrote:

> Attached patch updates the Breton spelling dictionary.

Thanks.  I have included it and generated new spell files.

--
Some of the well know MS-Windows errors:
	 ESLEEP  Operator fell asleep
	 ENOERR  No error yet
	 EDOLLAR  OS too expensive
	 EWINDOWS MS-Windows loaded, system in danger

  /// Bram Moolenaar -- Bram@... -- 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

Patch 7.3.619
Problem:    When executing a shell command Vim may become slow to respond.
Solution:   Don't wait after every processed message. (idea by Yasuhiro
	     Matsumoto)
Files:     src/os_win32.c


*** ../vim-7.3.618/src/os_win32.c 2012-07-19 11:37:22.000000000 +0200
--- src/os_win32.c 2012-08-02 12:30:52.000000000 +0200
***************
*** 3319,3324 ****
--- 3319,3326 ----
  	     {
  		 TranslateMessage(&msg);
  		 pDispatchMessage(&msg);
+ 	 delay = 1;
+ 	 continue;
  	     }
  	     if (WaitForSingleObject(pi.hProcess, delay) != WAIT_TIMEOUT)
  		 break;
*** ../vim-7.3.618/src/version.c 2012-07-29 12:55:21.000000000 +0200
--- src/version.c 2012-08-02 12:29:08.000000000 +0200
***************
*** 716,717 ****
--- 716,719 ----
   {   /* Add new patch number below this line */
+ /**/
+     619,
   /**/

--
Some of the well know MS-Windows errors:
	 EMULTI  Multitasking attempted, system confused
	 EKEYBOARD Keyboard locked, try getting out of this one!
	 EXPLAIN  Unexplained error, please tell us what happened
	 EFUTURE  Reserved for our future mistakes

  /// Bram Moolenaar -- Bram@... -- 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

Ken Takata wrote:

> 2012/07/22 4:01:04 UTC+9 Ingo Karkat:
> > I like the different highlighting of added / changed / removed. Having a
> >
> > different group for the file name is probably less important, but would be
easy
> >
> > to add, too.
>
> I don't think it is important, but if you send me a pull request, I will
include it.
>
> > One more request, though: Wouldn't it be more appropriate to name the syntax
> >
> > "hgcommit", because it's more precise, and for future compatibility?
>
> OK, I changed the name from "hg" to "hgcommit".
> A patch for filetype.vim was also updated.
> https://gist.github.com/3129572
> (https://github.com/k-takata/hg-vim)
>
>
> Bram,
> I think it is now ready for inclusion.
> I hope this would be a help for hg users and also for Vim contributors.

Thanks!  I'll include it.

If you make improvements, please email me the new file.

--
Some of the well know MS-Windows errors:
	 EMEMORY  Memory error caused by..., eh...
	 ELICENSE Your license has expired, give us more money!
	 EMOUSE  Mouse moved, reinstall Windows
	 EILLEGAL Illegal error, you are not allowed to see this
	 EVIRUS  Undetectable virus found

  /// Bram Moolenaar -- Bram@... -- 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

Hi, I found the problem in indent/vim.vim.

>  elseif getline(lnum) =~ '^\s*aug\%[roup]' && getline(lnum) !~
'^\s*aug\%[roup]\s*!\=\s\+END'
>    let ind = ind + &sw
>  else
>    let line = getline(lnum)
>    let i = match(line,
'\(^\||\)\s*\(if\|wh\%[ile]\|for\|try\|cat\%[ch]\|fina\%[lly]\|fu\%[nction]\|el\\
%[seif]\)\>')
>    if i >= 0
>      let ind += &sw
>      if strpart(line, i, 1) == '|' && has('syntax_items')
>            \ && synIDattr(synID(lnum, i, 1), "name") =~ '\(Comment\|String\)$'
>        let ind -= &sw
>      endif
>    endif

The match uses "=~" and "!~" instead of "=~" and "!~".
So if set ignorecase, the indentation is wrong.
I fixed the problem. Would you check it?
Note: Same problem may be in other indentation plugins. But I don't check.

--
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

I was trying to get Vim to build with MSVC 2008 on a clean system with
all the optional extras.  One thing that doesn't work is the XPM
feature.

The Make_mvc.mak file recommeds:

# XPM - Include support for XPM signs
# You need to download or build  xpm.lib somehow.
# You can get the most recent version of libXpm-*.zip from
#   http://cgit.freedesktop.org/xorg/lib/libXpm


But that site is down.  I found an alternate xpm_w32 zip file on
ftp.gnu.org, but it does not include libXpm.lib and no way to build it.

Any suggestions?

--
hundred-and-one symptoms of being an internet addict:
197. Your desk collapses under the weight of your computer peripherals.

  /// Bram Moolenaar -- Bram@... -- 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

> # XPM - Include support for XPM signs
> # You need to download or build  xpm.lib somehow.
> # You can get the most recent version of libXpm-*.zip from
> #   http://cgit.freedesktop.org/xorg/lib/libXpm
>
>
> But that site is down.  I found an alternate xpm_w32 zip file on
> ftp.gnu.org, but it does not include libXpm.lib and no way to build it.


I have built libXpm some 8 years ago. It is available from
https://sites.google.com/site/khorser/opensource/vim/xpm.zip?attredirects=0&d=1
Is it possible to put the file on Vim ftp?

--
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

Sergey Khorev schrob am 02. Aug. 2012 um 20:26 Zeit:
> I have built libXpm some 8 years ago. It is available from
>
https://sites.google.com/site/khorser/opensource/vim/xpm.zip?attredirects=0&d=1


It does not compile though. It says it can't find xpm.h although the
directory is correctly added per -I parametert.

--
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

Patch 7.3.620
Problem:    Building with recent Ruby on Win32 doesn't work.
Solution:   Add a separate argument for the API version. (Yasuhiro Matsumoto)
Files:     src/Make_ming.mak, src/Make_mvc.mak


*** ../vim-7.3.619/src/Make_ming.mak 2012-07-06 13:40:44.000000000 +0200
--- src/Make_ming.mak 2012-08-02 17:02:34.000000000 +0200
***************
*** 260,266 ****
   #   DYNAMIC_RUBY=yes (to load the Ruby DLL dynamically)
   #   RUBY_VER=[Ruby version, eg 16, 17] (default is 16)
   #   RUBY_VER_LONG=[Ruby version, eg 1.6, 1.7] (default is 1.6)
! #     You must set RUBY_VER_LONG when change RUBY_VER.
   #RUBY=c:/ruby
   ifdef RUBY
   ifndef DYNAMIC_RUBY
--- 260,268 ----
   #   DYNAMIC_RUBY=yes (to load the Ruby DLL dynamically)
   #   RUBY_VER=[Ruby version, eg 16, 17] (default is 16)
   #   RUBY_VER_LONG=[Ruby version, eg 1.6, 1.7] (default is 1.6)
! #     You must set RUBY_VER_LONG when changing RUBY_VER.
! #     You must set RUBY_API_VER version to RUBY_VER_LONG.
! #     Don't set ruby API version to RUBY_VER like 191.
   #RUBY=c:/ruby
   ifdef RUBY
   ifndef DYNAMIC_RUBY
***************
*** 273,278 ****
--- 275,283 ----
   ifndef RUBY_VER_LONG
   RUBY_VER_LONG = 1.6
   endif
+ ifndef RUBY_API_VER
+ RUBY_API_VER = $(subst .,,$(RUBY_VER_LONG))
+ endif

   ifndef RUBY_PLATFORM
   ifeq ($(RUBY_VER), 16)
***************
*** 288,296 ****

   ifndef RUBY_INSTALL_NAME
   ifeq ($(RUBY_VER), 16)
! RUBY_INSTALL_NAME = mswin32-ruby$(RUBY_VER)
   else
! RUBY_INSTALL_NAME = msvcrt-ruby$(RUBY_VER)
   endif
   endif

--- 293,301 ----

   ifndef RUBY_INSTALL_NAME
   ifeq ($(RUBY_VER), 16)
! RUBY_INSTALL_NAME = mswin32-ruby$(RUBY_API_VER)
   else
! RUBY_INSTALL_NAME = msvcrt-ruby$(RUBY_API_VER)
   endif
   endif

*** ../vim-7.3.619/src/Make_mvc.mak 2012-02-22 16:01:53.000000000 +0100
--- src/Make_mvc.mak 2012-08-02 17:42:31.000000000 +0200
***************
*** 63,68 ****
--- 63,70 ----
   #   RUBY_VER=[Ruby version, eg 16, 17] (default is 18)
   #   RUBY_VER_LONG=[Ruby version, eg 1.6, 1.7] (default is 1.8)
   #     You must set RUBY_VER_LONG when change RUBY_VER.
+ #     You must set RUBY_API_VER to RUBY_VER_LONG.
+ #     Don't set ruby API version to RUBY_VER like 191.
   #
   # Tcl interface:
   #   TCL=[Path to Tcl directory]
***************
*** 807,834 ****
   !ifndef RUBY_VER_LONG
   RUBY_VER_LONG = 1.8
   !endif

   !if $(RUBY_VER) >= 18
   !ifndef RUBY_PLATFORM
   RUBY_PLATFORM = i386-mswin32
   !endif
   !ifndef RUBY_INSTALL_NAME
! RUBY_INSTALL_NAME = msvcrt-ruby$(RUBY_VER)
   !endif
   !else
   !ifndef RUBY_PLATFORM
   RUBY_PLATFORM = i586-mswin32
   !endif
   !ifndef RUBY_INSTALL_NAME
! RUBY_INSTALL_NAME = mswin32-ruby$(RUBY_VER)
   !endif
   !endif # $(RUBY_VER) >= 18

   !message Ruby requested (version $(RUBY_VER)) - root dir is "$(RUBY)"
   CFLAGS = $(CFLAGS) -DFEAT_RUBY
   RUBY_OBJ = $(OUTDIR)\if_ruby.obj
! !if $(RUBY_VER) >= 190
! RUBY_INC = /I "$(RUBY)\include\ruby-$(RUBY_VER_LONG)\$(RUBY_PLATFORM)" /I
"$(RUBY)\include\ruby-$(RUBY_VER_LONG)"
   !else
   RUBY_INC = /I "$(RUBY)\lib\ruby\$(RUBY_VER_LONG)\$(RUBY_PLATFORM)"
   !endif
--- 813,843 ----
   !ifndef RUBY_VER_LONG
   RUBY_VER_LONG = 1.8
   !endif
+ !ifndef RUBY_API_VER
+ RUBY_API_VER = $(RUBY_VER_LONG:.=)
+ !endif

   !if $(RUBY_VER) >= 18
   !ifndef RUBY_PLATFORM
   RUBY_PLATFORM = i386-mswin32
   !endif
   !ifndef RUBY_INSTALL_NAME
! RUBY_INSTALL_NAME = msvcrt-ruby$(RUBY_API_VER)
   !endif
   !else
   !ifndef RUBY_PLATFORM
   RUBY_PLATFORM = i586-mswin32
   !endif
   !ifndef RUBY_INSTALL_NAME
! RUBY_INSTALL_NAME = mswin32-ruby$(RUBY_API_VER)
   !endif
   !endif # $(RUBY_VER) >= 18

   !message Ruby requested (version $(RUBY_VER)) - root dir is "$(RUBY)"
   CFLAGS = $(CFLAGS) -DFEAT_RUBY
   RUBY_OBJ = $(OUTDIR)\if_ruby.obj
! !if $(RUBY_VER) >= 19
! RUBY_INC = /I "$(RUBY)\lib\ruby\$(RUBY_VER_LONG)\$(RUBY_PLATFORM)" /I
"$(RUBY)\include\ruby-$(RUBY_VER_LONG)" /I
"$(RUBY)\include\ruby-$(RUBY_VER_LONG)\$(RUBY_PLATFORM)"
   !else
   RUBY_INC = /I "$(RUBY)\lib\ruby\$(RUBY_VER_LONG)\$(RUBY_PLATFORM)"
   !endif
*** ../vim-7.3.619/src/version.c 2012-08-02 12:31:40.000000000 +0200
--- src/version.c 2012-08-02 21:20:28.000000000 +0200
***************
*** 716,717 ****
--- 716,719 ----
   {   /* Add new patch number below this line */
+ /**/
+     620,
   /**/

--
hundred-and-one symptoms of being an internet addict:
199. You read this entire list of symptoms, looking for something
      that doesn't describe you.

  /// Bram Moolenaar -- Bram@... -- 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

Patch 7.3.621
Problem:    Compiler warnings on 64 bit windows.
Solution:   Add type casts. (Mike Williams)
Files:     src/ex_docmd.c, src/search.c


*** ../vim-7.3.620/src/ex_docmd.c 2012-07-27 21:12:03.000000000 +0200
--- src/ex_docmd.c 2012-08-02 21:19:22.000000000 +0200
***************
*** 3392,3398 ****
       /* Find start of last argument (argument just before cursor): */
       p = buff;
       xp->xp_pattern = p;
!     len = STRLEN(buff);
       while (*p && p < buff + len)
       {
  	 if (*p == ' ' || *p == TAB)
--- 3392,3398 ----
       /* Find start of last argument (argument just before cursor): */
       p = buff;
       xp->xp_pattern = p;
!     len = (int)STRLEN(buff);
       while (*p && p < buff + len)
       {
  	 if (*p == ' ' || *p == TAB)
*** ../vim-7.3.620/src/search.c 2012-07-29 12:55:21.000000000 +0200
--- src/search.c 2012-08-02 21:20:02.000000000 +0200
***************
*** 4621,4627 ****
  	     {
  		 /* searching backwards, so set pos to last line and col */
  		 pos.lnum = curwin->w_buffer->b_ml.ml_line_count;
! 	 pos.col  = STRLEN(ml_get(curwin->w_buffer->b_ml.ml_line_count));
  	     }
  	 }

--- 4621,4628 ----
  	     {
  		 /* searching backwards, so set pos to last line and col */
  		 pos.lnum = curwin->w_buffer->b_ml.ml_line_count;
! 	 pos.col  = (colnr_T)STRLEN(
! 			 ml_get(curwin->w_buffer->b_ml.ml_line_count));
  	     }
  	 }

*** ../vim-7.3.620/src/version.c 2012-08-02 21:21:43.000000000 +0200
--- src/version.c 2012-08-02 21:23:13.000000000 +0200
***************
*** 716,717 ****
--- 716,719 ----
   {   /* Add new patch number below this line */
+ /**/
+     621,
   /**/

--
hundred-and-one symptoms of being an internet addict:
200. You really believe in the concept of a "paperless" office.

  /// Bram Moolenaar -- Bram@... -- 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

> It does not compile though. It says it can't find xpm.h although the
> directory is correctly added per -I parametert.

You didn't mention how you tried to build Vim, here is how I did it:
nmake -f Make_mvc.mak GUI=yes CSCOPE=yes NETBEANS=yes XPM=e:\hg\xpm

E:\HG\vim\src>dir /B /S e:\hg\xpm
e:\hg\xpm\include
e:\hg\xpm\lib
e:\hg\xpm\include\simx.h
e:\hg\xpm\include\xpm.h
e:\hg\xpm\lib\libXpm.lib

--
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

Sergey Khorev wrote:

> > # XPM - Include support for XPM signs
> > # You need to download or build  xpm.lib somehow.
> > # You can get the most recent version of libXpm-*.zip from
> > #   http://cgit.freedesktop.org/xorg/lib/libXpm
> >
> >
> > But that site is down.  I found an alternate xpm_w32 zip file on
> > ftp.gnu.org, but it does not include libXpm.lib and no way to build it.
>
>
> I have built libXpm some 8 years ago. It is available from
>
https://sites.google.com/site/khorser/opensource/vim/xpm.zip?attredirects=0&d=1

Thanks.  I tried and it builds with MSVC 2008.  Don't know how to try if
it actually works.

> Is it possible to put the file on Vim ftp?

OK, I'll put it here: ftp://ftp.vim.org/pub/vim/pcextra/xpm.zip

Can you give some information about what it was build with?  I suppose
it only works for 32 bits builds?

--
hundred-and-one symptoms of being an internet addict:
201. When somebody asks you where you are, you tell them in which chat room.

  /// Bram Moolenaar -- Bram@... -- 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

Patch 7.3.622
Problem:    XPM library for Win32 can't be found.
Solution:   Suggest using the one from the Vim ftp site.
Files:     src/Make_mvc.mak


*** ../vim-7.3.621/src/Make_mvc.mak 2012-08-02 21:21:43.000000000 +0200
--- src/Make_mvc.mak 2012-08-02 21:45:52.000000000 +0200
***************
*** 281,287 ****

   !ifdef XPM
   # XPM - Include support for XPM signs
! # you can get xpm.lib from http://iamphet.nm.ru/xpm or create it yourself
   XPM_OBJ   = $(OBJDIR)/xpm_w32.obj
   XPM_DEFS  = -DFEAT_XPM_W32
   XPM_LIB   = $(XPM)\lib\libXpm.lib
--- 281,291 ----

   !ifdef XPM
   # XPM - Include support for XPM signs
! # You need to download or build  xpm.lib somehow.
! # You can get the most recent version of libXpm-*.zip from
! #   http://cgit.freedesktop.org/xorg/lib/libXpm
! # from which you must build xpm.lib yourself
! #   OR get and unpack: ftp://ftp.vim.org/pub/vim/pcextra/xpm.zip
   XPM_OBJ   = $(OBJDIR)/xpm_w32.obj
   XPM_DEFS  = -DFEAT_XPM_W32
   XPM_LIB   = $(XPM)\lib\libXpm.lib
*** ../vim-7.3.621/src/version.c 2012-08-02 21:24:38.000000000 +0200
--- src/version.c 2012-08-02 21:46:43.000000000 +0200
***************
*** 716,717 ****
--- 716,719 ----
   {   /* Add new patch number below this line */
+ /**/
+     622,
   /**/

--
hundred-and-one symptoms of being an internet addict:
202. You're amazed to find out Spam is a food.

  /// Bram Moolenaar -- Bram@... -- 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

Sergey Khorev schrob am 02. Aug. 2012 um 21:31 Zeit:
> nmake -f Make_mvc.mak GUI=yes CSCOPE=yes NETBEANS=yes XPM=e:\hg\xpm


Ah, I used relative folders. My fault, thanks!

--
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

I have a new PC with Windows 7 that I want to use to build Vim for
distribution.  It's a 64 bit system but I first want to build 32 bit
binaries.

I have installed MS C++ Express 2008, since the binaries from this
compiler run on most systems.  Building the normal console and GUI
versions works fine.

Now building with all the interfaces.  I installed:
Active State Perl 5.14 for x86
Python 2.7.3 (using Windows installer from python.org)
Python 3.2.3 (using Windows installer from python.org)
Ruby 1.9.2  (from www.garbagecollect.jp, see help file)
	 Rename include dir from 1.9.1 to 1.9.2
	 Remove check for _MSC_VER from config.h
	 Copy bin/msvcrt-ruby191.dll to C:\Windows\msvcrt-ruby192.dll
TCL 8.5.12  ActiveState Windows installer
XPM: get from the ftp site: ftp://ftp.vim.org/pub/vim/pcextra/xpm.zip
	 just unpack the zip archive and use the dir name

The Ruby install has 1.9.1 files even though I installed 1.9.2, very
confusing. I just renamed the files.

The XPM support now works thanks to Sergey.

I did some simple "hello world" tests and all appear to work, except
for Perl:
	 :perl VIM::Msg("Hello")
Vim crashes after printing "Hello".

Does anybody have an idea why the Perl 5.14 interface would load and do
something and then crash?

--
Spam seems to be something useful to novices.  Later you realize that
it's a bunch of indigestable junk that only clogs your system.
Applies to both the food and the e-mail!

  /// Bram Moolenaar -- Bram@... -- 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

Matsushita Shougo wrote:

> Hi, I found the problem in indent/vim.vim.
>
> >  elseif getline(lnum) =~ '^\s*aug\%[roup]' && getline(lnum) !~
'^\s*aug\%[roup]\s*!\=\s\+END'
> >    let ind = ind + &sw
> >  else
> >    let line = getline(lnum)
> >    let i = match(line,
'\(^\||\)\s*\(if\|wh\%[ile]\|for\|try\|cat\%[ch]\|fina\%[lly]\|fu\%[nction]\|el\\
%[seif]\)\>')
> >    if i >= 0
> >      let ind += &sw
> >      if strpart(line, i, 1) == '|' && has('syntax_items')
> >            \ && synIDattr(synID(lnum, i, 1), "name") =~
'\(Comment\|String\)$'
> >        let ind -= &sw
> >      endif
> >    endif
>
> The match uses "=~" and "!~" instead of "=~" and "!~".
> So if set ignorecase, the indentation is wrong.
> I fixed the problem. Would you check it?

Good idea.  I like the use of try/finally.

> Note: Same problem may be in other indentation plugins. But I don't check.

At least now we have a solution that can be applied to other plugins as
well.

--
panic("Foooooooood fight!");
	 -- In the kernel source aha1542.c, after detecting a bad segment list

  /// Bram Moolenaar -- Bram@... -- 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

From the vim_use list thread, "Activating Windows gVim from the
command line":

On 02 Aug 2012 21:32:33, Tony Mechelynck wrote:

> On 02/08/12 16:30, Ben Fritz wrote:

>> I do have one minor note which may save you some trouble in the future.
>>
>> You seem to think vim -c "/pattern" performs a '/' search. It
>> doesn't. What it is doing is specifying the first line of an ex
>> command range via a pattern. I'm not sure where it's documented
>> but specifying a single-line range with no command will just set
>> the cursor to that line.
>
> It has ho helptag of its own, but it is documented as :[range], just after
> ":help gg", in the section about up and down motions.

Attached in a proposed patch to add this tag.  The patch is based on
Vim 7.3.622.

Regards,
Gary

--
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

ÞÅÔ×ÅÒÇ, 2 Á×ÇÕÓÔÁ 2012 Ç., 16:07:29 UTC+4 ÐÏÌØÚÏ×ÁÔÅÌØ Shougo ÎÁÐÉÓÁÌ:
> Hi, I found the problem in indent/vim.vim.
>
>
>
> >  elseif getline(lnum) =~ '^\s*aug\%[roup]' && getline(lnum) !~
'^\s*aug\%[roup]\s*!\=\s\+END'
>
> >    let ind = ind + &sw
>
> >  else
>
> >    let line = getline(lnum)
>
> >    let i = match(line,
'\(^\||\)\s*\(if\|wh\%[ile]\|for\|try\|cat\%[ch]\|fina\%[lly]\|fu\%[nction]\|el\\
%[seif]\)\>')
>
> >    if i >= 0
>
> >      let ind += &sw
>
> >      if strpart(line, i, 1) == '|' && has('syntax_items')
>
> >            \ && synIDattr(synID(lnum, i, 1), "name") =~
'\(Comment\|String\)$'
>
> >        let ind -= &sw
>
> >      endif
>
> >    endif
>
>
>
> The match uses "=~" and "!~" instead of "=~" and "!~".
>
> So if set ignorecase, the indentation is wrong.
>
> I fixed the problem. Would you check it?
>
> Note: Same problem may be in other indentation plugins. But I don't check.

Why don't fix the problem by explicitely using "[=!][~=][#?]" everywhere? I just
always use "#" and "?" for string comparison, no matter whether it is "=~", "is"
or their opposites (yes, and I never use "=="/"!=" for string comparison). All
the problems should be fixed by running

     perl -p -i -e 's/(?<=[!=]~)(?![?#])/#/g unless /^\s*setlocal/' indent/*.vim
additionally reviewing changes when processing plugins for languages which
contain this operator. The result seem to be harmless:
http://bpaste.net/show/38213/.

--
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

On Thu, 2 Aug 2012, Bram Moolenaar wrote:

>
> I have a new PC with Windows 7 that I want to use to build Vim for
> distribution.  [...]
>
> Now building with all the interfaces.  I installed:
> [...]
> Ruby 1.9.2  (from www.garbagecollect.jp, see help file)
>  Rename include dir from 1.9.1 to 1.9.2
>  Remove check for _MSC_VER from config.h
>  Copy bin/msvcrt-ruby191.dll to C:\Windows\msvcrt-ruby192.dll
> [...]
>
> The Ruby install has 1.9.1 files even though I installed 1.9.2, very
> confusing. I just renamed the files.

Possibly important from a packaging perspective:

You shouldn't have to rename the files.  Ruby 1.9.2 and 1.9.3 are
"library compatible" with 1.9.1¹.  It seems like it'd be a PITA to have
to compile against a specific, non-standard version of Ruby.

The official (MRI) Ruby page points Windows users to:
http://rubyinstaller.org/

However, it's compiled against MinGW.  Is that one of the problems
(linking against different runtimes) the garbagecollect.jp version is
avoiding?  The help (:help ruby) didn't seem particularly clear as to
why the weird version was required.

--
Best,
Ben

¹:
Ruby 1.9.2 release notes -
http://www.ruby-lang.org/en/news/2010/08/18/ruby-1-9.2-released/
Explanation of 1.9.1 dir w/ 1.9.{2,3} - http://stackoverflow.com/a/8565831/82723

--
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

On Thursday, August 2, 2012 3:58:02 PM UTC-4, Bram Moolenaar wrote:
> I have a new PC with Windows 7 that I want to use to build Vim for
> distribution.  It's a 64 bit system but I first want to build 32 bit
> binaries.
> I have installed MS C++ Express 2008, since the binaries from this
> compiler run on most systems.  Building the normal console and GUI
> versions works fine.
> Now building with all the interfaces.  I installed:
> Active State Perl 5.14 for x86
> Python 2.7.3 (using Windows installer from python.org)
> Python 3.2.3 (using Windows installer from python.org)
> Ruby 1.9.2  (from www.garbagecollect.jp, see help file)
> TCL 8.5.12  ActiveState Windows installer
> XPM: get from the ftp site: ftp://ftp.vim.org/pub/vim/pcextra/xpm.zip
> The Ruby install has 1.9.1 files even though I installed 1.9.2, very
> I did some simple "hello world" tests and all appear to work, except
> for Perl:
>  :perl VIM::Msg("Hello")
> Vim crashes after printing "Hello".
> Does anybody have an idea why the Perl 5.14 interface would load and do
> something and then crash?

No idea about the crash, but here is some additional information:
I have successfully built many vims through 7.3.618 on Windows 7 and have both
python 2.7.3 from python.org and self-built perls 5.14 and now 5.16.  The same
:perl VIM::Msg("Hello") has always worked without crashing.  Compiled with MS C
compiler from SDK 7.1.  Same compiler used to builed the perls.

--
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

I send e-mail few weeks ago. But I couldn't get replies.
Bram, what's best way to fix this?

On Wednesday, June 20, 2012 6:55:16 PM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
>
>
> > When using auto completion on php or C with user's autocmd, it's
>
> > affected from user's autocmd.
>
> > For example, If user want to show up quickfix, below's autocmd is
>
> > useful.
>
> >
>
> > autocmd QuickfixCmdPost grep,grepadd,vimgrep if len(getqflist()) != 0 |
copen | endif
>
> >
>
> > phpcomplete, ccomplete call vimgrep to find somewhat to complete. So
>
> > quickfix show up with finish of vimgrep.
>
> > Below is a patch. Please check.
>
>
>
> I'll include the part for ccomplete.vim.  Please contact the authors of
>
> the scripts, they might not see this message or know that their file is
>
> affected.
>
>
>
> --
>
> It was recently discovered that research causes cancer in rats.
>
>
>
>  /// Bram Moolenaar -- Bram@... -- 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

> Why don’t fix the problem by explicitely using “[=!][~=][#?]” everywhere? I
just always use “#” and “?” for string comparison, no matter whether it is “=~”,
“is” or their opposites (yes, and I never use “==”/“!=” for string comparison).
All the problems should be fixed by running
>

Because, indent/vim.vim(and I think other plugins too) uses match(). This
functions also uses 'ignorecase' option.
I can't fix it easily. So I used try finally block and changed ignorecase
option.

>
>
>     perl -p -i -e 's/(?<=[!=]~)(?![?#])/#/g unless /^\s*setlocal/'
indent/*.vim
>
> additionally reviewing changes when processing plugins for languages which
contain this operator. The result seem to be harmless:
http://bpaste.net/show/38213/.

So I think your changes is incomplete.

Thanks your reply.

--
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