On So, 19 Jan 2014, Anhad Jai Singh wrote:
> When I do 'o' (plain old 'o', no fancy mappings nothing, the deafult
> open-INSERT-mode and take me to the next line 'o'), at a specific location
> in a specific file, vim hits 100% CPU usage, becomes unresponsive and needs
> to be killed.
>
> After some discussion on the #vim on freenode, :tek0 and :accolade helped
> narrow it down to the syntax highlighting. :syntax off makes the "bug"
> disappear.
>
>
> Steps to reproduce:
>
> 1. vim main.php
> 2. Go to line 48, on the closing '}' bracket.
> 3. hit 'o'
> 4. open top, watch vim hit 100% CPU usage.
>
>
> I'm attaching:
>
> 1. The file "main.php"
> 2. vim --version's output
> 3. my .vimrc
>
> Some of the debugging output requested on #vim, which may be useful again:
>
> Q: What does :map o give you? A: :map o gives No mapping found.
> Q: do you get anything for :au InsertEnter A: No.
> Q: any difference if you `:set foldmethod=manual`? A: No.
> Q: what's the filetype? A: filetype=php
I can't reproduce it. Some things to check:
Is there an easy way to reproduce it by starting from vim -u NONE -N (I
tried with your sample .vimrc, but that didn't trigger the bug).
Does it make a difference, when using :set re=1
There were a couple of more patches since your Version. Can you still
reproduce the problem with the latest version?
Best,
Christian
--
Wind und Wellen sind immer auf der Seite des besseren Seefahrers.
-- Edward Gibbon
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
