Enabling highlight module seems to affect indentation?

[tlamarre91]

Thanks for the awesome plugin. nvim-treesitter's highlighting for my typescript/typescriptreact files is excellent!

But it looks like me and a couple others are not having the greatest experience with TS/TSX indentation. So I've turned off the indent module, but I notice that even with it off, the highlight module seems to be affecting indentation.

I've commented out any settings related to indentation in my init.vim, and I'm toggling the nvim-treesitter highlight module on and off, and this is what I'm seeing:

• With the highlight module turned off with :TSDisableAll highlight, I get one indentation behavior (which happens to be correct)
• With the highlight module turned on with :TSEnableAll highlight, I get another indentation behavior (which happens to be wrong)

Disregarding whether the behavior is right or not, my expectation was that indentation behavior would not be affected by the highlight module. Now if that's not correct, please let me know! But it seemed like buggy behavior to me so I thought I'd ask about it.

Basically, my question is: is there something I'm failing to do, to get my desired behavior of highlighting-without-indentation?

I realize that I've provided zero details to help with debugging, which is because I'm assuming this is just some silly config error on my end. If it sounds like a bug, I can try to provide more info.

Here's my :checkhealth nvim_treesitter output if it helps:

health#nvim_treesitter#check
========================================================================
## Installation
  - OK: `tree-sitter` found  0.19.4 (parser generator, only needed for :TSInstallFromGrammar)
  - OK: `node` found v14.16.1 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl" }
  - OK: Neovim was compiled with tree-sitter runtime ABI version 13 (required >=13). Parsers must be compatible with runtime ABI.

## Parser/Features H L F I
  - supercollider  ✓ ✓ ✓ ✓ 
  - toml           ✓ ✓ ✓ ✓ 
  - graphql        ✓ . . ✓ 
  - javascript     ✓ ✓ ✓ ✓ 
  - devicetree     ✓ ✓ ✓ ✓ 
  - ruby           ✓ ✓ ✓ ✓ 
  - svelte         ✓ . ✓ ✓ 
  - r              ✓ ✓ . . 
  - bash           ✓ ✓ ✓ . 
  - vue            ✓ . ✓ . 
  - beancount      ✓ . ✓ . 
  - latex          ✓ . ✓ . 
  - jsonc          ✓ ✓ ✓ ✓ 
  - php            ✓ ✓ ✓ ✓ 
  - clojure        ✓ ✓ . . 
  - java           ✓ ✓ . ✓ 
  - bibtex         ✓ . ✓ ✓ 
  - cpp            ✓ ✓ ✓ ✓ 
  - kotlin         ✓ . . . 
  - zig            ✓ ✓ ✓ ✓ 
  - dart           ✓ ✓ . ✓ 
  - html           ✓ ✓ ✓ ✓ 
  - julia          ✓ ✓ . . 
  - yaml           ✓ ✓ ✓ ✓ 
  - ledger         ✓ . ✓ ✓ 
  - json           ✓ ✓ ✓ ✓ 
  - c              ✓ ✓ ✓ ✓ 
  - css            ✓ . ✓ ✓ 
  - python         ✓ ✓ ✓ ✓ 
  - gdscript       ✓ ✓ . . 
  - go             ✓ ✓ ✓ ✓ 
  - lua            ✓ ✓ ✓ ✓ 
  - ql             ✓ ✓ . ✓ 
  - gomod          ✓ . . . 
  - ocaml          ✓ ✓ ✓ . 
  - query          ✓ ✓ ✓ ✓ 
  - comment        ✓ . . . 
  - jsdoc          ✓ . . . 
  - ocaml_interface✓ ✓ ✓ . 
  - regex          ✓ . . . 
  - verilog        ✓ ✓ ✓ . 
  - ocamllex       ✓ . . . 
  - sparql         ✓ ✓ ✓ ✓ 
  - teal           ✓ ✓ ✓ ✓ 
  - typescript     ✓ ✓ ✓ ✓ 
  - fennel         ✓ ✓ . . 
  - rst            ✓ ✓ . . 
  - nix            ✓ ✓ ✓ . 
  - turtle         ✓ ✓ ✓ ✓ 
  - glimmer        ✓ . . . 
  - tsx            ✓ ✓ ✓ ✓ 
  - rust           ✓ ✓ ✓ ✓ 
  - erlang         . . . . 
  - c_sharp        ✓ . . . 

[theHamsta]

@kyazdani42 do you have a possible explanation for this weird interaction?

[kyazdani42]

i think it's because the highlight module disable syntax right ?

[tlamarre91]

Ooh, thanks! Yes, when I say :syntax on after opening a file, my indentation behavior changes to be more like I expect. I didn't realize that setting was relevant, since it didn't seem to matter whether it was in my init.vim or not. (I guess the highlight module disables it when opening a file, though I'm not seeing where that happens.)

I'm assuming there's a reason for disabling syntax, even if I don't know enough to guess it. If I just enable it anyway, am I going to break anything important?

Thanks for your help!

[theHamsta]

The highlight module has a config option additional_vim_regex_highlighting which will prevent syntax from being deactivated

[tlamarre91]

Well that is just dandy! Thanks a bunch.