How should we handle such cases? Options: - wait for Bram to fix all cases
- make those view regex use the old engine (in the ruby case there are only 4 making the difference) With syntime they are easy to find - fix all of those problems by implementing regexengine=999: run both expressions 5 times, take times, then settle on the faster engine for this regex. This may choose the wrong one, but is more likely to choose the faster one. This would immediately allow all users to use the new regex engine by default - find out whether there is a way to simplify the syntax files. Eventually benchmark them all on common files, make the results public, to make maintainers aware about which ones are particularly slow. There are huge differences right now. 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.
