Pham Huy Hoang 107e61afb7 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.		2023-10-25 18:18:50 +02:00
..
folds.scm	fix(php): add missing php fold query	2022-12-06 10:58:45 +01:00
highlights.scm	refactor: Remove all (ERROR) @error captures	2023-10-25 18:18:50 +02:00
indents.scm	refactor: improve readability	2023-10-15 14:34:32 -04:00
injections.scm	fixup: php injections	2023-08-12 17:45:44 +02:00
locals.scm	lint(locals): use #set! to keep query linter happy	2023-06-22 08:39:17 +02:00