Is there a way to customize how dap-view shows a stack trace element when hitting enter on a stack trace line in the Threads view?

[NickJAllen]

When I set a breakpoint that gets hit and then I go to the Threads tab and see my stack trace I often want to navigate up and down the stack trace and see what is going on. When I press enter on a particular line it is opened in a new window if it's not the current file. If I have a stack trace that spans 10 different files and I navigate up and down I end up with 10 split windows and it's very confusing. I would like that it just opens the location in the current window I'm using for editing my source code. I would like to be in charge when splits are created or not. Is there a setting for this? I couldn't find anything on the documentation about this and not sure if it's a bug, missing feature or I'm just missing something.

Otherwise this is really great!

[igorlfs]

Is there a way to customize how dap-view shows a stack trace element when hitting enter on a stack trace line in the Threads view?

Yes! Check the FAQ

The TLDR is that you can use nvim-dap-view's switchbuf setting (which is based on :help 'switchbuf').

When I press enter on a particular line it is opened in a new window if it's not the current file.

The default behavior is to:

1. Search for the requested buffer on any tab*
2. If the buffer could not be found, try to use the last window (if it's valid)
3. Else, create a new "top-level" split (a new window on "top" of every other window in the current tab)

I think that what you're describing might be neovim switching tabs (i.e., behavior 1). This can be specially confusing if you're using a "buffer line" plugin. If that's the case, you have some options:

• You could tweak switchbuf to skip the search for buffers in other tabs (check the docs)
• You also tweak the follow_tab setting (e.g., you can set it to true). The FAQ also goes a little more into depth about that.

I navigate up and down I end up with 10 split windows and it's very confusing

Just to reiterate: are you sure these windows are not in different tabs?

I would like to be in charge when splits are created or not.

Luckily, you can! In addition to the "bare" variants of switchbuf, it can also be a function!

I couldn't find anything on the documentation about this

Let me know if there are improvements to be made to the docs. If you're feeling like it, you can send a PR! As you can imagine, you're not the first one to get confused by switchbuf. Unfortunately, it's impossible to ship a default that pleases everyone.

[NickJAllen]

I only have one tab open so I don't think it's because it's finding something in a different tab. Thanks for pointing me to the configuration option to change the behavior! I will try changing it seeing if that fixes the problem but this seems more like a bug to me because I just have only one window one tab and its constantly splitting my window when the file to jump to is not visible in any of the windows on my screen.

[igorlfs]

more like a bug to me because I just have only one window one tab and its constantly splitting my window when the file to jump to is not visible in any of the windows on my screen

Can you please share a minimal reproduction?

[NickJAllen]

Thanks for your help and sorry again I missed this in the documentation. I fixed it by using this setting:

{
'igorlfs/nvim-dap-view',
---@module 'dap-view'
---@type dapview.Config
opts = {
switchbuf = 'useopen,usetab,uselast',
},
}

From the source code it seems the default is 'usetab,uselast'. 'usetab' sohuld be the same as useopen though so I think there must be a bug in the usetab implementation. Because putting useopen before it shouldn't change anything as usetab should behave the same as useopen and then only consider other tabs (which I have none) if that fails.

[NickJAllen]

Actually I thought changing it that way fixed it but it seems it did not. I still get splits all the time. I guess there is a bug in the code and I'll see if I can track it down.

[igorlfs]

Can you please share a minimal repro?

[NickJAllen]

Can you please share a minimal repro?

It's hard to track down exactly when it happens. It seems to happen when I'm doing normal work and not trying to reproduce it. If I can find steps I'll let you know.

[igorlfs]

If I can find steps I'll let you know.

When you do, can you open a new issue? As that's unrelated to the original question