On Thursday, December 4, 2014 3:51:05 PM UTC-6, John Whitley wrote: > ### Repro steps > > 1. From this gist[1], download the files `killvimrc` and `longline.rb`. > 2. Run vim with `vim -u killvimrc longline.rb`. > > ### Actual results > > `vim` locks up at 100% CPU utilization and must be killed with `kill -9 ...` > > ### Expected results > > File loads and is editable. > > ### Notes > > Reproduced with vim 7.4.488 and 7.4.540 (hg HEAD at time of writing). > > This issue appears to be tied to the vim ruby syntax file. Removing the line > `syntax on` from `killvimrc` allows the file to load, as does renaming > `longline.rb` to `longline.txt`. As expected, loading the file as a .txt > file and running `:set ft=ruby` will trigger the lockup. >
https://groups.google.com/forum/#!topic/vim_dev/tTyRMSakpSI >From this discussion, Ruby highlight was especially slow after the >introduction of the new regex engine, due to frequent use of zero-width >look-behind assertions \@<! and \@<= without using the character-limiting >features added to address the problem of their slowness in the new engine >(:help /\@<= , :help /\@<! , scroll down to the part about limiting by bytes). Looking at https://github.com/vim-ruby/vim-ruby/blob/master/syntax/ruby.vim this issue was never fully addressed, only for one of the occurrences. Perhaps a new issue should be created in the bug tracker on that github to use the byte limits wherever possible. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
