7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/components/vim/patches/7197223.patch Thu Sep 13 10:13:43 2012 +0200
@@ -0,0 +1,13 @@
+--- runtime/syntax/dtrace.vim Thu Sep 13 09:27:02 2012
++++ runtime/syntax/dtrace.vim Thu Sep 13 09:27:15 2012
[email protected]@ -40,8 +40,8 @@
+ " XXX: This allows a probe description to end with ',', even if it's not
+ " followed by another probe.
+ " XXX: This doesn't work if followed by a comment.
+-let s:oneProbe = '\%(BEGIN\|END\|ERROR\|\S\{-}:\S\{-}:\S\{-}:\S\{-}\)\_s*'
+-exec 'syn match dtraceProbe "'.s:oneProbe.'\%(,\_s*'.s:oneProbe.'\)*\ze\_s\%({\|\/[^*]\|\%$\)"'
++let s:oneProbe = '\%(BEGIN\|END\|ERROR\|\S\{-}:\S\{-}:\S\{-}:\S*\)\_s*'
++exec 'syn match dtraceProbe "'.s:oneProbe.'\%(,\_s*'.s:oneProbe.'\)*\ze\_s*\%({\|\/[^*]\|\_s*\S\|\%$\)"'
+
+ " Note: We have to be careful to not make this match /* */ comments.
+ " Also be careful not to eat `c = a / b; b = a / 2;`. We use the same