Column value outside range when selecting @function.inner or @block.outer

[Elias-Gill]

Description

There seems to be an issue when using @inner or @outer textobjects with certain parsers (e.g., Go, Markdown) with objects like functions or blocks.

In some cases, the selection fails with an error because the calculated column is out of range.

Steps to reproduce

• Neovim version: NVIM v0.12.0-dev-1305+ga0c60e819d, Build type: Debug, LuaJIT 2.1.1753364724
• Treesitter version: 0.25.8 (f2f197b6b27ce75c280c20f131d4f71e906b86f7)
• Plugin version: commit @1b2d85d3 (main branch)

1. In a Go file, create a simple function such as:

   func main() {
       // some irrelevant code here
   }

2. Call:

   require("nvim-treesitter-textobjects.select").select_textobject("@function.inner", "textobjects")

3. Observe the following error:

   Output

   E5108: Lua: ...r-textobjects/lua/nvim-treesitter-textobjects/select.lua:32: Column value outside range
   stack traceback:
           [C]: in function 'nvim_win_set_cursor'
           ...r-textobjects/lua/nvim-treesitter-textobjects/select.lua:32: in function 'update_selection'
           ...r-textobjects/lua/nvim-treesitter-textobjects/select.lua:174: in function 'select'
           .../elias/.config/nvim/lua/elias/plugins/lsp/treeSitter.lua:101: in function <.../treeSitter.lua:100>
   

This also occurs with @block.outer in Markdown files.

Root cause (tentative)

From some debugging, the problem seems to be in the update_selection function inside
nvim-treesitter-textobjects/lua/nvim-treesitter-textobjects/select.lua:

api.nvim_win_set_cursor(0, { end_row + 1, end_col - end_col_offset })

The issue appears when end_col - end_col_offset is less than 0 or greater than the actual number of columns in the line, causing nvim_win_set_cursor to fail.

Hotfix

As a quick workaround in my local environment, I added a bounds check before setting the cursor:

-- Check bounds
local line_length = vim.fn.col({ end_row + 1, '$' }) - 1
end_col = end_col - end_col_offset
if end_col < 0 then
  end_col = 0
end
if end_col > line_length then
  end_col = line_length
end

-- Position is 1, 0 indexed.
api.nvim_win_set_cursor(0, { start_row + 1, start_col })
vim.cmd('normal! o')
api.nvim_win_set_cursor(0, { end_row + 1, end_col })

This prevents the error and makes selections work again, at least in the cases I tested.

Notes

• I am not deeply familiar with the internals of this plugin, so I cannot say for certain if this is the proper place to fix the bug.
• This hotfix simply allowed me to continue using my local environment without errors.
• If this is indeed the right place for the fix, I’d be happy to open a PR with the change.

[w1ck3dg0ph3r]

Ending selection on the previous line in inclusive mode works better for me (didn't test on a lot of parsers/queries though):

  end_col = end_col - end_col_offset
  if end_col < 0 then
    end_row = end_row - 1
    local prev_line = vim.api.nvim_buf_get_lines(0, end_row, end_row + 1, false)[1]
    end_col = string.len(prev_line) - 1
  end

[kiyoon]

I don't have the issue anymore. At least not with the example you provided. is this already fixed?

[w1ck3dg0ph3r]

The issue still reproduces for me on main (2e5b873) with the slightly modified example:

func foo() error {
	return nil
}

Selecting @function.inner produces select.lua:32: Column value outside range: the range from the query is { 1, 1, 2, 0 } which results in nvim_win_set_cursor(0, {3, -1}) for the end of selection.

[kiyoon]

Fixed by #828