diff options
| author | Santos Gallegos <stsewd@protonmail.com> | 2020-09-05 19:06:09 -0500 |
|---|---|---|
| committer | Thomas Vigouroux <tomvig38@gmail.com> | 2020-09-07 18:24:55 +0200 |
| commit | 9c456edb3ad24be92a54b42545df8f0d0ee4c71b (patch) | |
| tree | eb49ea2ff33a236758f14328683e326702720dff /parser | |
| parent | Fold: respect max_fold_level from 'foldnestmax' (diff) | |
| download | nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.tar nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.tar.gz nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.tar.bz2 nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.tar.lz nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.tar.xz nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.tar.zst nvim-treesitter-9c456edb3ad24be92a54b42545df8f0d0ee4c71b.zip | |
Incremental selection: fix skipping some nodes
The range from ts nodes are a little different than
neovim's nodes. They start at 0 and the end is exclusive.
For example, a nvim range (1, 3, 2, 4) is the equivalent to the ts
range (0, 2, 1, 4).
Since we may hit parent nodes that have the same range as its child,
we skip those till we find one that actually changes the selection
(since this is the relevant part for the user).
Fixes https://github.com/nvim-treesitter/nvim-treesitter/issues/232
Diffstat (limited to 'parser')
0 files changed, 0 insertions, 0 deletions