2022-03-30 17:08:07 +02:00
|
|
|
[
|
|
|
|
(compound_statement)
|
2023-03-11 03:49:19 +01:00
|
|
|
(declaration_list)
|
2022-03-30 17:08:07 +02:00
|
|
|
(field_declaration_list)
|
|
|
|
(enumerator_list)
|
|
|
|
(parameter_list)
|
|
|
|
(init_declarator)
|
|
|
|
(expression_statement)
|
|
|
|
] @indent
|
|
|
|
|
|
|
|
[
|
|
|
|
"case"
|
|
|
|
"}"
|
|
|
|
"]"
|
2023-08-11 12:24:37 +02:00
|
|
|
")"
|
2022-03-30 17:08:07 +02:00
|
|
|
] @outdent
|
|
|
|
|
|
|
|
(if_statement
|
|
|
|
consequence: (_) @indent
|
|
|
|
(#not-kind-eq? @indent "compound_statement")
|
|
|
|
(#set! "scope" "all"))
|
|
|
|
(while_statement
|
|
|
|
body: (_) @indent
|
|
|
|
(#not-kind-eq? @indent "compound_statement")
|
|
|
|
(#set! "scope" "all"))
|
|
|
|
(do_statement
|
|
|
|
body: (_) @indent
|
|
|
|
(#not-kind-eq? @indent "compound_statement")
|
|
|
|
(#set! "scope" "all"))
|
|
|
|
(for_statement
|
|
|
|
")"
|
|
|
|
(_) @indent
|
|
|
|
(#not-kind-eq? @indent "compound_statement")
|
|
|
|
(#set! "scope" "all"))
|
2023-08-11 12:24:37 +02:00
|
|
|
|
|
|
|
(parameter_list
|
|
|
|
. (parameter_declaration) @anchor
|
|
|
|
(#set! "scope" "tail")) @align
|
2023-09-19 16:29:52 +02:00
|
|
|
(argument_list
|
|
|
|
. (_) @anchor
|
|
|
|
(#set! "scope" "tail")) @align
|
2023-12-03 19:47:01 +01:00
|
|
|
; These are a bit opinionated since some people just indent binary/ternary expressions spanning multiple lines.
|
|
|
|
; Since they are only triggered when a newline is inserted into an already complete binary/ternary expression,
|
|
|
|
; this should happen rarely, so it is not a big deal either way.
|
|
|
|
; Additionally, adding these queries has the advantage of preventing such continuation lines from being used
|
|
|
|
; as the baseline when the `hybrid` indent heuristic is used (which is desirable since their indentation is so inconsistent).
|
|
|
|
(binary_expression
|
|
|
|
(#set! "scope" "tail")) @anchor @align
|
|
|
|
(conditional_expression
|
|
|
|
"?" @anchor
|
|
|
|
(#set! "scope" "tail")) @align
|