bug: Opening files in the Threads tab results in a new big ass window on the top of all existing windows

[voltangle]

Did you check docs and existing issues?

• I have read all the plugin docs
• I have searched the existing issues
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.11.4 Release

Operating system/version

macOS Sequoia 15.1

Describe the bug

https://github.com/user-attachments/assets/a9b86ded-42ef-495c-9fb2-d429b4465130
Essentially this

Steps To Reproduce

1. Start debugging session
2. Pause execution
3. Go to Threads tab
4. Enter any file

Expected Behavior

Would be better to instead open it in the last focused window, so if I switch from a window to the dap-view window and then try opening any file from that tab, it would open the contents in that window from which I switched over before

[igorlfs]

Hello,

Thanks for reporting! This is indeed unintended behavior.

To control which window will be used, nvim-dap-view offers its switchbuf setting: you can search for the buffer in the current tab, use the last window, open a new tab... You can also combine these alternatives as fallbacks: search for the buffer in the current tab, but if it's not found, open a new tab. You can even write your own function to have full control!

The default setting is rather conservative, though: it just tries to find the buffer on any tab (preferably the current one). If it's not found, there's a "universal fallback" that just opens a new window. And the behavior you're experiencing comes from this universal fallback: it assumes the layout isn't very "complex" and just spawns a gigantic window -- which was intended to "fix" the layout when the only windows open came from nvim-dap-view itself. However, this assumption isn't great, evidently.

I'll push a fix to no longer rely on this assumption, but I encourage you to take a look at the switchbuf setting, which allows you to achieve your expected behavior.

I'm also considering tweaking the default switchbuf to include uselast, which should vastly reduce the odds of using the universal fallback...

[igorlfs]

I'll push a fix to no longer rely on this assumption, but I encourage you to take a look at the switchbuf setting, which allows you to achieve your expected behavior

Done with 9293d1d

I'm also considering tweaking the default switchbuf to include uselast, which should vastly reduce the odds of using the universal fallback...

Trying that with 666b2a1 to see how it goes...

[voltangle]

Thanks a lot man!