Plans for v2

[igorlfs]

Hey folks!

By now, if I had to guess, you're having an amazing experience when debugging in neovim! To make this experience even more wonderful, I'm planning a release for a v2.

Wait, a v2? Where's the v1?

We are now in "pre-release" mode: if you notice any bugs, please report them (specially for the new features). This will last about a week or two, and then we're good to go! 🚀

v2

The current ideas for v2 are:

• "Multi-head" mode: users can configure multiple windows, each with their own sections. The new default layout will change to resemble Zed's newly released debugger: 3 windows at the bottom, the splits being as follows: Breakpoint|Exceptions|Threads + Scopes|REPL|Watches + Console.
• Configuration overhaul. Lots of options were created "organically" as people requested features, and they may not make sense in the "big picture". For instance, windows.height makes no sense if windows.position is "left"/"right" (similarly with windows.terminal.width). That's a small discrepancy which I may fix in the meantime, but there are others: why does the winbar table holds so many options?

Share any other ideas below!

[betaboon]

it might be against your design philosophy, but i'd like to be able to do this:

instead of having one window that contains everything (and optionally "merge" the console into it), allow defining N windows that contain M sections.

eg:

windows = {
  {
    sections = { 'console', 'repl' },
  },
  {
    sections = { 'watches', 'scopes' },
  },
  {
    sections = { 'breakpoints', 'exceptions', 'threads' },
  },
},

[igorlfs]

it might be against your design philosophy, but i'd like to be able to do this:

Hey, that sounds nice, actually. Not against my design philosophy at all.

instead of having one window that contains everything (and optionally "merge" the console into it), allow defining N windows that contain M sections.

Do you have any ideas for handling the layout? Currently, users can position both windows in any combination they want, but with an arbitrary number of windows that would be more complex, I assume

[betaboon]

not really sure.

could either be like now, all windows in the bottom, side-by-side, or with something like left, bottom,right or so.

[igorlfs]

Do you have any ideas for handling the layout?

I think we can once again take inspiration from nvim-dap-ui. Its default configuration is

  layouts = {
    {
      -- You can change the order of elements in the sidebar
      elements = {
        -- Provide IDs as strings or tables with "id" and "size" keys
        {
          id = "scopes",
          size = 0.25, -- Can be float or integer > 1
        },
        { id = "breakpoints", size = 0.25 },
        { id = "stacks", size = 0.25 },
        { id = "watches", size = 0.25 },
      },
      size = 40,
      position = "left", -- Can be "left" or "right"
    },
    {
      elements = {
        "repl",
        "console",
      },
      size = 10,
      position = "bottom", -- Can be "bottom" or "top"
    },
  },

The only change we would have to make is that we could take an array of ids. We would still use the top-level split logic we are currently using. Should also consider having layouts per debug adapter (which is a feature request from nvim-dap-ui).

One thing that isn't obvious with this approach is what should take precedence: elements on the sidebar or at the bottom / top.

[paulhdk]

Enable the UI by default

From #76 (reply in thread).

Given that the default config in the README doesn't set any options and there was no mention of any toggle commands, I just assumed the plugin was going to show the UI whenever I started a dap session.
It only opening a terminal, which could just be an empty buffer, was misleading to me here.

I'd venture a guess and say that most people installing this plugin are interested in having a UI. But I can't back that claim up with numbers of course :)
I'd personally even going as far as saying that I'd expect the terminal to to be integrated into the tab bar by default, but that's really just preference I think.

So, I'm in favour of enabling the UI by default and then mentioning in the documentation that it can also be toggled.

What do you think?

[igorlfs]

Enable the UI by default

...

What do you think?

As discussed in #76, that's a no-go. But I outlined some suggestions for the "terminal vs other views" situation.

[PhilippFeO]

"Multi-head" mode: users can configure multiple windows, each with their own sections. The new default layout will change to resemble Zed's newly released debugger: 3 windows at the bottom, the splits being as follows: Breakpoint|Exceptions|Threads + Scopes|REPL|Watches + Console.

Having one window with sections is the reason why I switched from Dapui. As long as this configuration remains, I am

having an amazing experience when debugging in neovim!

[igorlfs]

As long as this configuration remains

Just to be clear, having the option to use a single window isn't going anywhere. The purpose of "multi-head" mode is just to also give the option to use multiple windows.

[PhilippFeO]

Just to be clear, having the option to use a single window isn't going anywhere. The purpose of "multi-head" mode is just to also give the option to use multiple windows.

I was expecting this! :) Just wanted to share my use case, so you know how and why people like your plugin! ❤️

[assaf758]

This plugin is a major improvement over the nvim-dap-ui experience, thanks!
I would say the main win is in saving precious screen asset, with automatic zoom on the view of interest.
I'm not sure how doable this is - but in fact I would have love to have this approach as infra - so the user can add other views (neotest, quickfix comes to mind)

[igorlfs]

Hey,

I'm not sure how doable this is - but in fact I would have love to have this approach as infra - so the user can add other views (neotest, quickfix comes to mind)

This should already be technically doable via custom views (though it may need some tweaking). If you wanna go ahead and try to implement one of your suggestions as a custom view, we could add an "integrations" section to the docs.

with automatic zoom on the view of interest

Is this also a feature request? Could you elaborate?

[PhilippFeO]

This plugin is a major improvement over the nvim-dap-ui experience, thanks!
I would say the main win is in saving precious screen asset, with automatic zoom on the view of interest.

These are 1:1 my reasons! It is also simpler to use/set up than Dapui.

[assaf758]

This should already be technically doable via custom views (though it may need some tweaking). If you wanna go ahead and try to implement one of your suggestions as a custom view, we could add an "integrations" section to the docs.

Nice, I will give it a try

Is this also a feature request? Could you elaborate?

No, I was just mentioning the (obvious) fact that when you select view, it is displayed on the whole window.