Opening ANY Telescope picker with chrisbra/NrrwRgn SOFT-LOCKS nvim

[nKUhrF6D]

Description

Run the reproduction steps and you'll get an error from Telescope relating to some invalid buffer ID. The editor will then be soft-locked. The display is bugged and you have to restart.

Neovim version

NVIM v0.10.2
Build type: RelWithDebInfo
LuaJIT 2.1.1727870382

Operating system and version

Linux

Telescope version / branch / rev

master

checkhealth telescope

==============================================================================
telescope: health#telescope#check

Checking for required plugins ~
- OK plenary installed.
- WARNING nvim-treesitter not found. (Required for `:Telescope treesitter`.)

Checking external dependencies ~
- OK rg: found ripgrep 14.1.1
- WARNING fd: not found. Install [sharkdp/fd](https://github.com/sharkdp/fd) for extended capabilities

===== Installed extensions ===== ~

Steps to reproduce

1. Install Plenary, Telescope and NrrwRgn,
2. Start nvim,
3. Type in text,
4. Select it in visual mode,
5. Run command :NR!
6. Ensure that there is only one window open with the NrrwRegion buffer inside it,
7. Try to run :Telescope files or any other picker,
8. You will get the error described above and Neovim will soft-lock.

Expected behavior

That it doesn't soft-lock the editor.

Actual behavior

You get an error like the following, and the editor becomes soft-locked:

Error executing Lua callback: ...avigation/start/telescope.nvim/lua/telescope/pickers.lua:580: Invalid buffer id: 4
stack traceback:
        [C]: in function 'nvim_buf_set_lines'
        ...avigation/start/telescope.nvim/lua/telescope/pickers.lua:580: in function 'find'
        ...tart/telescope.nvim/lua/telescope/builtin/__internal.lua:1006: in function 'v'
        ...tart/telescope.nvim/lua/telescope/builtin/__internal.lua:1515: in function 'v'
        ...tion/start/telescope.nvim/lua/telescope/builtin/init.lua:587: in function <...tion/start/telescope.nvim/lua/telescope/builtin/init.lua:546>
        ...avigation/start/telescope.nvim/lua/telescope/command.lua:188: in function 'run_command'
        ...avigation/start/telescope.nvim/lua/telescope/command.lua:259: in function 'load_command'
        ...ack/navigation/start/telescope.nvim/plugin/telescope.lua:108: in function <...ack/navigation/start/telescope.nvim/plugin/telescope.lua:107>

You then have to run :qa! to exit and restart. The editor is rendered inoperable by the bug.

Minimal config

No config whatsoever is necessary to reproduce this issue.

[jamestrew]

No config whatsoever is necessary to reproduce this issue.

You should provide the minimal config for this

Install Plenary, Telescope and NrrwRgn,

This is how we test things to ensure both you and I are using the exact same neovim config and that it is reproducible with said minimal config.

[nKUhrF6D]

@jamestrew No config is needed to install vim plugins, and I was clear in my original post that no config at all is needed to reproduce this issue. Simply add the two plugins into your rtp and follow the reproduction steps. I reproduced this myself on a clean neovim instance (with no config) when I first made the issue.

I've since moved on from Telescope because it's sloppy, and now, poorly maintained. But I decided to test this again to see if it's still broken.

Version information:

soft	version
neovim	NVIM v0.11.0, LuaJIT 2.1.1741730670
telescope	commit a4ed825
plenary	commit 857c5ac

It's still broken.

[jamestrew]

FYI no config means nvim --clean which this clearly isn't.

We ask for minimal configs and we can just copy and run to reproduce the issue because

1. We're volunteering for time, it'd be great if we didn't have to construct our config, manually downloading plugins and reading setup instructions for them
2. We commonly find that the issue is related to something not mentioned in the bug report. If people don't provide us with a minimal config, normally that means they didn't try so then it becomes a whole game of debugging their entire config. Which we don't always have time to do.