vim-patch:8.2.1297: when a test fails it's often not easy to see where

Problem:    When a test fails it's often not easy to see what the call stack
            is.
Solution:   Add more entries from the call stack in the exception message.
a5d0423fa1

Use docs from latest Vim.
This commit is contained in:
zeertzjq
2022-08-14 06:32:00 +08:00
parent 1c164689a4
commit 98ab0bb5f7
9 changed files with 77 additions and 43 deletions

View File

@@ -99,7 +99,7 @@ void do_debug(char_u *cmd)
xfree(debug_newval);
debug_newval = NULL;
}
char *sname = estack_sfile();
char *sname = estack_sfile(false);
if (sname != NULL) {
msg(sname);
}
@@ -324,7 +324,7 @@ static void do_checkbacktracelevel(void)
debug_backtrace_level = 0;
msg(_("frame is zero"));
} else {
char *sname = estack_sfile();
char *sname = estack_sfile(false);
int max = get_maxbacktrace_level(sname);
if (debug_backtrace_level > max) {
@@ -337,7 +337,7 @@ static void do_checkbacktracelevel(void)
static void do_showbacktrace(char_u *cmd)
{
char *sname = estack_sfile();
char *sname = estack_sfile(false);
int max = get_maxbacktrace_level(sname);
if (sname != NULL) {
int i = 0;