Clear... and Reset... Breakpoints both re-ask questions

[benthorner]

Description

The following two functions behave the same for me:

• vimspector#ClearBreakpoints()
• vimspector#ResetExceptionBreakpoints()

After running either of them, I need to re-answer questions e.g.

I can't find any other function to clear breakpoints, which is all I want to do.

(Really cool plugin by the way 🚀.)

Is it reproducible in vim?

Reproducible in Vim

Works with clean config?

Yes

Sample project works?

Reproducible with sample project

Minimal Reproduction

Start Vim with minimal vimrc:

cd ~/.vim/bundle/vimspector/support/test/node/typescript

vim --clean -Nu ~/.vim/bundle/vimspector/support/minimal_vimrc src/index.ts

Then start Vimspector (may prompt to install js-debug - accept):

:call vimspector#Launch()

Then try both of the two Clear/Reset functions:

:call vimspector#ClearBreakpoints()
:call vimspector#ResetExceptionBreakpoints()

In each case need to re-answer questions (the problem) - accept.

Expected Behaviour

Not have to press more times to re-answer breakpoint questions.

I was assuming this should be the case for ClearBreakpoints, but it's not. I don't feel strongly about which function achieves this though: an existing function or a new function would be great.

Actual Behaviour

Have to press more times to re-answer breakpoint questions.

Additional information

No response

Installation Type

Plugin Manager (git clone)

Vimspector version

0da16c6

Debug Info

Log file

Vim version

VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Apr 14 2025 19:19:34)
macOS version - arm64
Included patches: 1-1300
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               +file_in_path      +mouse_urxvt       -tag_any_white
+arabic            +find_in_path      +mouse_xterm       -tcl
+autocmd           +float             +multi_byte        +termguicolors
+autochdir         +folding           +multi_lang        +terminal
-autoservername    -footer            -mzscheme          +terminfo
-balloon_eval      +fork()            +netbeans_intg     +termresponse
+balloon_eval_term +gettext           +num64             +textobjects
-browse            -hangul_input      +packages          +textprop
++builtin_terms    +iconv             +path_extra        +timers
+byte_offset       +insert_expand     +perl              +title
+channel           +ipv6              +persistent_undo   -toolbar
+cindent           +job               +popupwin          +user_commands
-clientserver      +jumplist          +postscript        +vartabs
+clipboard         +keymap            +printer           +vertsplit
+cmdline_compl     +lambda            +profile           +vim9script
+cmdline_hist      +langmap           -python            +viminfo
+cmdline_info      +libcall           +python3           +virtualedit
+comments          +linebreak         +quickfix          +visual
+conceal           +lispindent        +reltime           +visualextra
+cryptv            +listcmds          +rightleft         +vreplace
+cscope            +localmap          +ruby              +wildignore
+cursorbind        +lua               +scrollbind        +wildmenu
+cursorshape       +menu              +signs             +windows
+dialog_con        +mksession         +smartindent       +writebackup
+diff              +modify_fname      +sodium            -X11
+digraphs          +mouse             +sound             -xattr
-dnd               -mouseshape        +spell             -xfontset
-ebcdic            +mouse_dec         +startuptime       -xim
+emacs_tags        -mouse_gpm         +statusline        -xpm
+eval              -mouse_jsbterm     -sun_workshop      -xsmp
+ex_extra          +mouse_netterm     +syntax            -xterm_clipboard
+extra_search      +mouse_sgr         +tag_binary        -xterm_save
-farsi             -mouse_sysmouse    -tag_old_static
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
 3rd user vimrc file: "~/.config/vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/opt/homebrew/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X -DMACOS_X_DARWIN -mllvm -enable-constraint-elimination=0 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang -o vim -lm -lncurses -lsodium -liconv -lintl -framework AppKit -L/opt/homebrew/opt/lua/lib -llua5.4 -L/System/Library/Perl/5.34/darwin-thread-multi-2level/CORE -lperl -L/opt/homebrew/opt/python@3.13/Frameworks/Python.framework/Versions/3.13/lib/python3.13/config-3.13-darwin -lpython3.13 -framework CoreFoundation -lruby.3.4 -L/opt/homebrew/Cellar/ruby/3.4.2/lib

Python version

No response

Neovim diagnostics

Operating System

No response

Declaration

• I have read and understood CONTRIBUTING.md
• I have read and understood the CODE_OF_CONDUCT.md

[puremourning]

Clear breakouts clears all breakpoints including exception breakpoints.

Reset exception breakpoints just clears exception breakpoints.

You can:

• set your exception breakpoint preferences in the vimspector JSON file
• use the breakpoints window to toggle/disable or delete all line breakpoints

I don't see this as a bug, it's the behaviour I intended.

[benthorner]

Thanks for taking a look @puremourning 🙏.

I don't think I explained the issue clearly: I have set breakpoint preferences.

"breakpoints": {
  "exception": {
    "all": "N",
    "uncaught": "N"
  }
}

The preferences are working as expected, but only when I run vimspector#Launch(). When I run either of "Clear breakpoints" or "Reset exception breakpoints", I have to re-answer breakpoint questions.

Could you help me understand if there's some extra configuration I'm missing?

Happy to open a new issue and explain again if you'd prefer.

[puremourning]

It may be possible to have have clear just reinstate the configured breakpoints.

[benthorner]

@puremourning that would be ideal ➕.

Typically I set a bunch of breakpoints over time and then want a clean slate; finding and toggling each of them individually takes a while. I know there's the breakpoint list, but even with that it still takes many keystrokes.

Then I found "Clear/Reset [Exception] Breakpoints" and thought that would help.

I was surprised I had to re-answer breakpoint questions and wasn't sure if it that was intended behaviour for some reason.

[puremourning]

Please update the Issue with steps to reproduce using one of the sample projects in supports/examples, as requested in CONTRIBUTING.md and the issue template.

Reason: Checking the code I would have expected it to work the way I described, so I want to save myself time to understand the issue and solve it.

[benthorner]

@puremourning sure, updated the issue description ✅.

• Clarified commands to start Vim.
• Clarified command to launch Vimspector.
• Reiterated the two clear/reset commands.

In case it's helpful, I've attached ~/.vimspector.log here - just covers the above steps.

vimspector.log