components/vim/patches/7197223.patch
author Vladimir Marek <Vladimir.Marek@oracle.com>
Thu, 13 Sep 2012 10:12:30 +0200
branchs11-sru
changeset 2350 e2c992920a55
child 7049 e8d705cba87d
permissions -rw-r--r--
7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
2350
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     1
--- runtime/syntax/dtrace.vim	Thu Sep 13 09:27:02 2012
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     2
+++ runtime/syntax/dtrace.vim	Thu Sep 13 09:27:15 2012
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     3
@@ -40,8 +40,8 @@
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     4
 " XXX: This allows a probe description to end with ',', even if it's not
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     5
 " followed by another probe.
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     6
 " XXX: This doesn't work if followed by a comment.
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     7
-let s:oneProbe = '\%(BEGIN\|END\|ERROR\|\S\{-}:\S\{-}:\S\{-}:\S\{-}\)\_s*'
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     8
-exec 'syn match dtraceProbe "'.s:oneProbe.'\%(,\_s*'.s:oneProbe.'\)*\ze\_s\%({\|\/[^*]\|\%$\)"'
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
     9
+let s:oneProbe = '\%(BEGIN\|END\|ERROR\|\S\{-}:\S\{-}:\S\{-}:\S*\)\_s*'
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
    10
+exec 'syn match dtraceProbe "'.s:oneProbe.'\%(,\_s*'.s:oneProbe.'\)*\ze\_s*\%({\|\/[^*]\|\_s*\S\|\%$\)"'
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
    11
 
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
    12
 " Note: We have to be careful to not make this match /* */ comments.
e2c992920a55 7197223 vim shows high CPU usage when editing dtrace script with syntax highlighting enabled
Vladimir Marek <Vladimir.Marek@oracle.com>
parents:
diff changeset
    13
 " Also be careful not to eat `c = a / b; b = a / 2;`. We use the same