On Jan 25, 6:49 pm, Tony Mechelynck [EMAIL PROTECTED]
wrote:
thomas wrote:
BTW is there somethime like an Error autocommand?
Regards,
Thomas.
See :help exception-handling.
Best regards,
Tony.
I am shure he knows about that.
Anyway, who wants builtin quickfix use of vimscript ?
On Jan 26, 1:15 am, Dominique Pelle [EMAIL PROTECTED]
wrote:
(...)
map c-g 2c-g
(...)
Creating such a recursive mapping should perhaps give an error,
rather than causing infinite loops when triggering the mapping.
-- Dominique
What is more alarming then 100% cputime ? ;-)
-ap
Creating such a recursive mapping should perhaps give an error,
rather than causing infinite loops when triggering the mapping.
The infinite loop is actually a feature, and documented.
:help recursive_mapping
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
On Jan 26, 2008 12:21 AM, Ben Schmidt [EMAIL PROTECTED] wrote:
I've noticed that pressing CTRL-G while in visual mode,
causes vim to take 100% of the CPU.
I can interrupt it with CTRL-C.
Anybody else observing that?
Not me. 7.1.203
Ben.
Ah, sorry, false alert. Investigating
Hi,
I've noticed that pressing CTRL-G while in visual mode,
causes vim to take 100% of the CPU.
I can interrupt it with CTRL-C.
Anybody else observing that?
Steps to reproduce bug:
1/ press v command to enter visual mode
2/ press CTRL-G
3/ observe that vim takes 100% of CPU
I'm using
Patch 7.1.005, which altered the behavior of empty inner text objects
([], {}, etc.), broke one character ones ([x], { }, etc.). Pressing
cib inside of (x) is now inserts before the x, whereas before 7.1.005
it would delete the x first.
Cheers,
Tim Pope
I've noticed that pressing CTRL-G while in visual mode,
causes vim to take 100% of the CPU.
I can interrupt it with CTRL-C.
Anybody else observing that?
Not me. 7.1.203
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
