view src/testdir/test108.ok @ 14305:8a4c0ab88201 v8.1.0168

patch 8.1.0168: output of :marks is too short with multi-byte chars commit https://github.com/vim/vim/commit/9d5185bf9dfaef59e47c573a60044a21d5e29c0c Author: Bram Moolenaar <Bram@vim.org> Date: Sun Jul 8 17:57:34 2018 +0200 patch 8.1.0168: output of :marks is too short with multi-byte chars Problem: Output of :marks is too short with multi-byte chars. (Tony Mechelynck) Solution: Get more bytes from the text line.
author Christian Brabandt <cb@256bit.org>
date Sun, 08 Jul 2018 18:00:07 +0200
parents 8fc60af6dbf5
children a527110d5f56
line wrap: on
line source




- show backtrace:

  2 function Foo[2]
  1 Bar[2]
->0 Bazz
line 2: let var3 = "another var"

show variables on different levels:

6
  2 function Foo[2]
->1 Bar[2]
  0 Bazz
line 2: let var3 = "another var"
3
->2 function Foo[2]
  1 Bar[2]
  0 Bazz
line 2: let var3 = "another var"
1

- undefined vars:

undefined var3 on former level:
Error detected while processing function Foo[2]..Bar[2]..Bazz:
line    3:
E121: Undefined variable: var3
E15: Invalid expression: var3
here var3 is defined with "another var":
another var

undefined var2 on former level
Error detected while processing function Foo[2]..Bar:
line    3:
E121: Undefined variable: var2
E15: Invalid expression: var2
here var2 is defined with 10:
10

- backtrace movements:

  1 function Foo[2]
->0 Bar
line 3: End of function

next command cannot go down, we are on bottom

frame is zero

next command cannot go up, we are on top

frame at highest level: 1
->1 function Foo[2]
  0 Bar
line 3: End of function
fil is not frame or finish, it is file
"[No Name]" --No lines in buffer--

- relative backtrace movement

  1 function Foo[2]
->0 Bar
line 3: End of function
->1 function Foo[2]
  0 Bar
line 3: End of function

- go beyond limits does not crash

frame at highest level: 1
->1 function Foo[2]
  0 Bar
line 3: End of function
frame is zero
  1 function Foo[2]
->0 Bar
line 3: End of function

- final result 19:
19