Mercurial > vim

comparison runtime/doc/repeat.txt @ 7605:8fc60af6dbf5 v7.4.1102

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc Author: Bram Moolenaar <Bram@vim.org> Date: Sat Jan 16 15:40:53 2016 +0100 patch 7.4.1102 Problem: Debugger has no stack backtrace support. Solution: Add "backtrace", "frame", "up" and "down" commands. (Alberto Fanjul, closes https://github.com/vim/vim/issues/433)
author Christian Brabandt <cb@256bit.org>
date Sat, 16 Jan 2016 15:45:04 +0100
parents 9487ea110214
children abd64cf67bcf
comparison
equal deleted inserted replaced
7604:09a1aca8d980 7605:8fc60af6dbf5
1 *repeat.txt* For Vim version 7.4. Last change: 2015 Apr 13 1 *repeat.txt* For Vim version 7.4. Last change: 2016 Jan 16
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
481 on interrupt exceptions. 481 on interrupt exceptions.
482 *>finish* 482 *>finish*
483 finish Finish the current script or user function and come 483 finish Finish the current script or user function and come
484 back to debug mode for the command after the one that 484 back to debug mode for the command after the one that
485 sourced or called it. 485 sourced or called it.
486 *>bt*
487 *>backtrace*
488 *>where*
489 backtrace Show the call stacktrace for current debugging session.
490 bt
491 where
492 *>frame*
493 frame N Goes to N bactrace level. + and - signs make movement
494 relative. E.g., ":frame +3" goes three frames up.
495 *>up*
496 up Goes one level up from call stacktrace.
497 *>down*
498 down Goes one level down from call stacktrace.
486 499
487 About the additional commands in debug mode: 500 About the additional commands in debug mode:
488 - There is no command-line completion for them, you get the completion for the 501 - There is no command-line completion for them, you get the completion for the
489 normal Ex commands only. 502 normal Ex commands only.
490 - You can shorten them, up to a single character: "c", "n", "s" and "f". 503 - You can shorten them, up to a single character, unless more then one command
504 starts with the same letter. "f" stands for "finish", use "fr" for "frame".
491 - Hitting <CR> will repeat the previous one. When doing another command, this 505 - Hitting <CR> will repeat the previous one. When doing another command, this
492 is reset (because it's not clear what you want to repeat). 506 is reset (because it's not clear what you want to repeat).
493 - When you want to use the Ex command with the same name, prepend a colon: 507 - When you want to use the Ex command with the same name, prepend a colon:
494 ":cont", ":next", ":finish" (or shorter). 508 ":cont", ":next", ":finish" (or shorter).
509
510 The backtrace shows the hierarchy of function calls, e.g.:
511 >bt ~
512 3 function One[3] ~
513 2 Two[3] ~
514 ->1 Three[3] ~
515 0 Four ~
516 line 1: let four = 4 ~
517
518 The "->" points to the current frame. Use "up", "down" and "frame N" to
519 select another frame.
520
521 In the current frame you can evaluate the local function variables. There is
522 no way to see the command at the current line yet.
495 523
496 524
497 DEFINING BREAKPOINTS 525 DEFINING BREAKPOINTS
498 *:breaka* *:breakadd* 526 *:breaka* *:breakadd*
499 :breaka[dd] func [lnum] {name} 527 :breaka[dd] func [lnum] {name}