[UX] Setting a breakpoint, as the very first user action

[frou]

I remember when I used to use Visual Studio (classic, not VScode), once the thought entered my mind that I wanted to debug something, I would instinctively just click in the margin to set a breakpoint.

Although Dape supports clicking in the margin (or pressing C-x C-a b) to set a breakpoint, it seems that this cannot be my first action. I first have to do a dummy M-x dape RET, then cancel out of that Minibuffer UI with C-g, and only then can I set a breakpoint by mouse or keyboard.

What do you think about making it so that setting a breakpoint point can be the very first user action?

---

(I thought calling (dape-breakpoint-global-mode) in my init file was perhaps the answer, but it seems like that isn't an autoloaded function so doesn't necessarily exist at startup? Maybe you can set me straight on that)

[svaante]

Hello, and thank you for your interest in Dape!

You're right, that's quite a cumbersome way to remove breakpoints before running your program.
I've been using use-package, so I havent bumped into that issue myself (use-package is great).

I agree that dape-breakpoint-global-mode should probably be auto-loaded.

Edit:
I just added dape-breakpoint-global-mode to autoloads in a24820e thank you for the suggestion :)

[frou]

Thank you. I do actually (use-package dape ...) but I must admit I don't understand all the facets of the use-package DSL that contribute to the decision of whether a library is eagerly loaded or not. Should I be adding :demand t or something?

[frou]

I do actually (use-package dape ...) but I must admit I don't understand all the facets of the use-package DSL that contribute to the decision of whether a library is eagerly loaded or not. Should I be adding :demand t or something?

Resolved that. My tangled web there was because I was using :hook to do something I should have done using (add-hook ...) in the :config section.