Hi,
When I use the following command (for demonstration purposes):
au CursorMoved * norm! zz
When I now press or , 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 or
zz gets inserted.
Is there a wo
Thomas wrote:
Hi,
When I use the following command (for demonstration purposes):
au CursorMoved * norm! zz
When I now press or , 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 or
zz gets inserted.
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
Pr
Thomas wrote:
> When I use the following command (for demonstration purposes):
>
> au CursorMoved * norm! zz
>
> When I now press or , 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 or
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/
> V
":behave mswin" only sets a few options, but it is often used in
conjunction with ":source $VIMRUNTIME/mswin.vim", which sets a lot of
potentially dangerous mappings.
I only have behave mswin in my vimrc.
This happens with gvim -u NONE --noplugin.
When you do ":behave mswin" the shifted cur
Thomas wrote:
> > ":behave mswin" only sets a few options, but it is often used in
> > conjunction with ":source $VIMRUNTIME/mswin.vim", which sets a lot of
> > potentially dangerous mappings.
> I only have behave mswin in my vimrc.
>
> This happens with gvim -u NONE --noplugin.
>
> > When yo
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
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
--- 1
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 ac
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 t
11 matches
Mail list logo
