From c6f9f739d32084923c3031cbf6f581f8c8bf7fd2 Mon Sep 17 00:00:00 2001 From: Bram Moolenaar Date: Sun, 11 Feb 2018 19:06:26 +0100 Subject: patch 8.0.1505: debugger can't break on a condition Problem: Debugger can't break on a condition. (Charles Campbell) Solution: Add ":breakadd expr". (Christian Brabandt, closes #859) --- runtime/doc/repeat.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'runtime/doc/repeat.txt') diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index d0475b7da..2e9746bc6 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -806,6 +806,19 @@ DEFINING BREAKPOINTS < Note that this only works for commands that are executed when sourcing the file, not for a function defined in that file. +:breaka[dd] expr {expression} + Sets a breakpoint, that will break whenever the {expression} + evaluates to a different value. Example: > + :breakadd expr g:lnum + +< Will break, whenever the global variable lnum changes. + Note if you watch a |script-variable| this will break + when switching scripts, since the script variable is only + valid in the script where it has been defined and if that + script is called from several other scripts, this will stop + whenever that particular variable will become visible or + unaccessible again. + The [lnum] is the line number of the breakpoint. Vim will stop at or after this line. When omitted line 1 is used. -- cgit v1.2.1