From 107e61afb7129d637ea6c3c68b97a22194b0bf16 Mon Sep 17 00:00:00 2001 From: Pham Huy Hoang Date: Wed, 25 Oct 2023 16:45:14 +0900 Subject: refactor: Remove all `(ERROR) @error` captures As discussed in PR#5421, capturing `@error` is inconsistent, requiring deep nesting (or priority) in order to correctly have red backgrounds to it. Some queries has this capture, some don't. For consistency purposes, removing all of them is more preferable. For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)` to your custom queries. --- queries/python/highlights.scm | 3 --- 1 file changed, 3 deletions(-) (limited to 'queries/python') diff --git a/queries/python/highlights.scm b/queries/python/highlights.scm index 04398668e..de98dccbf 100644 --- a/queries/python/highlights.scm +++ b/queries/python/highlights.scm @@ -346,6 +346,3 @@ ;; https://docs.python.org/3/library/stdtypes.html "bool" "int" "float" "complex" "list" "tuple" "range" "str" "bytes" "bytearray" "memoryview" "set" "frozenset" "dict" "type" "object")) - -;; Error -(ERROR) @error -- cgit v1.2.3-70-g09d2