### 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. Bugreport.txt for the 7.4.488 run is in a separate gist at [2]. Also reported as neovim/neovim#1161 [3]. This appears to be related to earlier threads on long lines in the presence of syntax highlighting, and VIM 7.4 patches 497, 519, 526, 527. [4][5][6] [1] https://gist.github.com/jwhitley/080d53d3e6a83ce8fe61 [2] https://gist.github.com/jwhitley/2ecd483b0cb3cca0657c [3] https://github.com/neovim/neovim/issues/1611 [4] https://groups.google.com/forum/#!msg/vim_dev/Ge7eVpTuyx0/iYKt_rZB1v0J [5] https://groups.google.com/forum/#!msg/vim_dev/JjFYb7j1WBw/YMd3h6VLS90J [6] https://code.google.com/p/vim/issues/detail?id=274 -- John -- -- 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/d/optout.
