mirror of
https://github.com/vim/vim.git
synced 2025-09-26 04:04:07 -04:00
patch 9.0.1866: undo is synced after character find
Problem: Undo is synced after character find. Solution: Set no_u_sync when calling gotchars_nop(). closes: #13022 closes: #13024 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: zeertzjq <zeertzjq@outlook.com>
This commit is contained in:
committed by
Christian Brabandt
parent
3170342af3
commit
dccc29c228
@@ -570,7 +570,9 @@ normal_cmd_get_more_chars(
|
|||||||
// but when replaying a recording the next key is already in the
|
// but when replaying a recording the next key is already in the
|
||||||
// typeahead buffer, so record a <Nop> before that to prevent the
|
// typeahead buffer, so record a <Nop> before that to prevent the
|
||||||
// vpeekc() above from applying wrong mappings when replaying.
|
// vpeekc() above from applying wrong mappings when replaying.
|
||||||
|
++no_u_sync;
|
||||||
gotchars_nop();
|
gotchars_nop();
|
||||||
|
--no_u_sync;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
--no_mapping;
|
--no_mapping;
|
||||||
|
@@ -862,5 +862,15 @@ func Test_undo_after_write()
|
|||||||
call delete('Xtestfile.txt')
|
call delete('Xtestfile.txt')
|
||||||
endfunc
|
endfunc
|
||||||
|
|
||||||
|
func Test_undo_range_normal()
|
||||||
|
new
|
||||||
|
call setline(1, ['asa', 'bsb'])
|
||||||
|
let &l:undolevels = &l:undolevels
|
||||||
|
%normal dfs
|
||||||
|
call assert_equal(['a', 'b'], getline(1, '$'))
|
||||||
|
undo
|
||||||
|
call assert_equal(['asa', 'bsb'], getline(1, '$'))
|
||||||
|
bwipe!
|
||||||
|
endfunc
|
||||||
|
|
||||||
" vim: shiftwidth=2 sts=2 expandtab
|
" vim: shiftwidth=2 sts=2 expandtab
|
||||||
|
@@ -699,6 +699,8 @@ static char *(features[]) =
|
|||||||
|
|
||||||
static int included_patches[] =
|
static int included_patches[] =
|
||||||
{ /* Add new patch number below this line */
|
{ /* Add new patch number below this line */
|
||||||
|
/**/
|
||||||
|
1866,
|
||||||
/**/
|
/**/
|
||||||
1865,
|
1865,
|
||||||
/**/
|
/**/
|
||||||
|
Reference in New Issue
Block a user