Re: an idea for plugin development: strict mode
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 ? I think its a shame, that the editor isn't able to use one of it's very own features. -ap --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Pressing CTRL-G in visual mode causes vim to use 100% of the CPU.
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 --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Pressing CTRL-G in visual mode causes vim to use 100% of the CPU.
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 --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Pressing CTRL-G in visual mode causes vim to use 100% of the CPU.
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 further, I found the root cause, I had a silly recursive mapping in my ~/.vimrc: map c-g 2c-g I can't remember why I had such a senseless mapping. I suspect it was meant to be: map c-g gc-g I never use ctrl-g and did not notice the problem until today. I've removed the offending mapping from my ~/.vimrc and everything is now OK. Creating such a recursive mapping should perhaps give an error, rather than causing infinite loops when triggering the mapping. -- Dominique --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Pressing CTRL-G in visual mode causes vim to use 100% of the CPU.
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 vim-7.1 (patches 1-241) on Linux x86 built with configure --with-features=huge. -- Dominique --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Single character inner text objects broken by 7.1.005
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
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: Pressing CTRL-G in visual mode causes vim to use 100% of the CPU.
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 --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
