Mercurial > vim
view src/testdir/test108.ok @ 15255:19e79a1ed6b6 v8.1.0636
patch 8.1.0636: line2byte() gives wrong values with text properties
commit https://github.com/vim/vim/commit/b413d2e6a8cc7b1611a41bfa9462b986393ca5fe
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Dec 25 23:15:46 2018 +0100
patch 8.1.0636: line2byte() gives wrong values with text properties
Problem: line2byte() gives wrong values with text properties. (Bjorn Linse)
Solution: Compute byte offsets differently when text properties were added.
(closes #3718)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 25 Dec 2018 23:30:07 +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