view src/testdir/test108.ok @ 15450:bb421f682528 v8.1.0733

patch 8.1.0733: too many #ifdefs for the multi-byte feature commit https://github.com/vim/vim/commit/2be7cb73f66cf69659195d9a8ad4beaa359f2865 Author: Bram Moolenaar <Bram@vim.org> Date: Sat Jan 12 16:10:51 2019 +0100 patch 8.1.0733: too many #ifdefs for the multi-byte feature Problem: Too many #ifdefs for the multi-byte feature. Solution: Tentatively always enable the multi-byte feature. If you have a problem with this, please discuss on the Vim maillist.
author Bram Moolenaar <Bram@vim.org>
date Sat, 12 Jan 2019 16:15:04 +0100
parents a527110d5f56
children
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
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
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