BUG vim 7.0-204?: autocmd CusorMoved vs select/visual mode vs :behave mswin vs norm!

2007-03-25 Thread Thomas
Hi, When I use the following command (for demonstration purposes): au CursorMoved * norm! zz When I now press s-c-left or s-c-right, zz get inserted in the buffer. These cursor key seem to be set by :behave mswin. In summary: :au CursorMoved * norm! zz :behave mswin Press s-c-left or

Re: BUG vim 7.0-204?: autocmd CusorMoved vs select/visual mode vs :behave mswin vs norm!

2007-03-25 Thread A.J.Mechelynck
Thomas wrote: Hi, When I use the following command (for demonstration purposes): au CursorMoved * norm! zz When I now press s-c-left or s-c-right, zz get inserted in the buffer. These cursor key seem to be set by :behave mswin. In summary: :au CursorMoved * norm! zz :behave mswin Press

segfault in vim7

2007-03-25 Thread pancake
I've found a bug in vim, i have no time for debugging, but here's an example and a minor backtrace: looks like %edx is used as a pointer and this pointer is NULL. No idea if this should be fixed in this way, but here's some info: [EMAIL PROTECTED] vim -r /tmp/ Vim: Caught deadly signal SEGV

Re: BUG vim 7.0-204?: autocmd CusorMoved vs select/visual mode vs :behave mswin vs norm!

2007-03-25 Thread Bram Moolenaar
Thomas wrote: When I use the following command (for demonstration purposes): au CursorMoved * norm! zz When I now press s-c-left or s-c-right, zz get inserted in the buffer. These cursor key seem to be set by :behave mswin. In summary: :au CursorMoved * norm! zz :behave mswin

Re: segfault in vim7

2007-03-25 Thread Bram Moolenaar
Pancake wrote: I've found a bug in vim, i have no time for debugging, but here's an example and a minor backtrace: looks like %edx is used as a pointer and this pointer is NULL. No idea if this should be fixed in this way, but here's some info: [EMAIL PROTECTED] vim -r /tmp/ Vim:

Re: segfault in vim7

2007-03-25 Thread pancake
sorry for the noise. it's fixed in 7.0-1.201 or it was a building problem. On Sun, 25 Mar 2007 14:59:52 +0200 Bram Moolenaar [EMAIL PROTECTED] wrote: Pancake wrote: I've found a bug in vim, i have no time for debugging, but here's an example and a minor backtrace: looks like %edx

patch 7.0.220

2007-03-25 Thread Bram Moolenaar
Patch 7.0.220 Problem:Crash when using winnr('#') in a new tab page. (Andy Wokula) Solution: Check for not finding the window. Files: src/eval.c *** ../vim-7.0.219/src/eval.c Tue Feb 20 03:18:20 2007 --- src/eval.c Sun Mar 25 17:43:53 2007 *** *** 15769,15775 ---

Re: GVim Crash

2007-03-25 Thread A.J.Mechelynck
Andy Wokula wrote: GVim7 (Win32) crashes if I do the following: clean startup :new :tabnew :call winnr(#) happens with or without 219 patches included Andy also on Linux with gvim 7.0.219 called as gvim -N -u NONE and also when replacing :call by :echo. Note that the last accessed

Re: BUG vim 7.0-204?: autocmd CusorMoved vs select/visual mode vs :behave mswin vs norm!

2007-03-25 Thread Thomas
When in Select mode you are still in sort-of Normal mode. Your autocommand will have to take care of mode stuff by itself. You can use CTRL-\ CTRN-N to make sure you are in Normal mode. Okay, I now wrapped the norm! commands in a function and check via mode() if we are in select mode and