Try this file: https://raw.github.com/jeremywohl/iphone-scripts/master/appstore_reviews
copy paste it into a .rb file. This feel very slow to me. I can watch Vim drawing blocks of lines. Using regexpengine=1 everything is as fast as ever. patches: 1-1115 It might make sense to introduce little benchmarking for regular expressions. Eg open such a file, then list which regex took how much cpu cycles or time. Bram: You've collected a lot of files for checking. Can you commit them all to the vim repository, so that we also can implement a simple benchmark which does - syn on | syn off 100 times? That would be enough to find that big regressions. Editing ruby this way is unbearable (sry). If we know that some use cases are slower - how to cope with it? Is the new engine not "ready enough" for such reports yet? If it should be, what about introducing bencharking regular expressions? add cpu cycle counter and dump them on exit? Then you'd at least know for which expressions (ruby case) to select the old engine. Its not a problem that the new engine is not ready yet, but we should find a way to cope with it - and introduce ways to find regriessions fast. >From now on I've set regexpengine=1 in my .vimrc, too. Marc Weber -- -- 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.
