nvim-treesitter/runtime/queries/v/locals.scm

(function_declaration
  name: (identifier) @local.definition.function) ;@function

(var_declaration
  var_list: (expression_list
    (reference_expression
      (identifier) @local.definition.var)))

(function_declaration
  name: (identifier) @local.definition.function)

(const_declaration
  (const_definition
    name: (identifier) @local.definition.var))

(identifier) @local.reference

((call_expression
  name: (reference_expression
    (identifier)) @local.reference)
  (#set! reference.kind "call"))

((call_expression
  name: (selector_expression
    field: (reference_expression
      (identifier) @local.definition.function)))
  (#set! reference.kind "call"))

(source_file) @local.scope

(function_declaration) @local.scope

(if_expression) @local.scope

(block) @local.scope

(for_statement) @local.scope
chore: format queries 2024-01-21 22:05:44 +09:00			`(function_declaration`
			`name: (identifier) @local.definition.function) ;@function`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
refactor(v)!: update upstream repository 2023-07-04 04:12:21 -04:00			`(var_declaration`
refactor(format): drop extra indentation for field 2024-03-21 20:44:35 +09:00			`var_list: (expression_list`
			`(reference_expression`
			`(identifier) @local.definition.var)))`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
chore: format queries 2024-01-21 22:05:44 +09:00			`(function_declaration`
			`name: (identifier) @local.definition.function)`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
chore: query formatting 2024-01-06 15:05:50 +09:00			`(const_declaration`
			`(const_definition`
			`name: (identifier) @local.definition.var))`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(identifier) @local.reference`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
chore: query formatting 2024-01-06 15:05:50 +09:00			`((call_expression`
refactor(format): drop extra indentation for field 2024-03-21 20:44:35 +09:00			`name: (reference_expression`
			`(identifier)) @local.reference)`
chore: query formatting 2024-01-06 15:05:50 +09:00			`(#set! reference.kind "call"))`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
			`((call_expression`
refactor(format): drop extra indentation for field 2024-03-21 20:44:35 +09:00			`name: (selector_expression`
			`field: (reference_expression`
			`(identifier) @local.definition.function)))`
chore: query formatting 2024-01-06 15:05:50 +09:00			`(#set! reference.kind "call"))`
feat(vlang): initial support Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta 2022-02-22 17:36:44 +03:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(source_file) @local.scope`
chore: query formatting 2024-01-06 15:05:50 +09:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(function_declaration) @local.scope`
chore: query formatting 2024-01-06 15:05:50 +09:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(if_expression) @local.scope`
chore: query formatting 2024-01-06 15:05:50 +09:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(block) @local.scope`
chore: query formatting 2024-01-06 15:05:50 +09:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(for_statement) @local.scope`