aboutsummaryrefslogtreecommitdiff
path: root/test/functional/lua/utility_functions_spec.lua
diff options
context:
space:
mode:
authorPedro L. Ramos <pedro.2.ramos@nokia.com>2019-01-07 15:48:44 +0000
committerJustin M. Keyes <justinkz@gmail.com>2019-01-10 08:50:07 +0100
commit57c7e1d4a0d7285d9de5b9035e91f546654268da (patch)
tree78b6da87e2f0aecb4ac85b0c0d0921b8f7995639 /test/functional/lua/utility_functions_spec.lua
parent1ca2c8950fe33654f046183516a123fe0606b4e8 (diff)
downloadrneovim-57c7e1d4a0d7285d9de5b9035e91f546654268da.tar.gz
rneovim-57c7e1d4a0d7285d9de5b9035e91f546654268da.tar.bz2
rneovim-57c7e1d4a0d7285d9de5b9035e91f546654268da.zip
vim-patch:8.1.0648: custom operators can't act upon forced motion
Problem: Custom operators can't act upon a forced motion. (Christian Wellenbrock) Solution: Add the forced motion to the mode() result. (Christian Brabandt, closes vim/vim#3490) https://github.com/vim/vim/commit/5976f8ff00efcb3e155a89346e44f2ad43d2405a closes #8667 closes #9476 Christian Wellenbrock: > For (most) built in text objects it's possible to force operation on > them to be linewise, for example by using `dVab` (`:h o_V`, > `motion_force`). When using custom text objects (defined as mappings > by plugins for example), this doesn't currently work. > > Example: > > onoremap x viw > > Open a file with a few lines each containing some words. With the > cursor on any word, try: > > 1. `dw` (builtin) deletes some characters > 2. `dVw` (builtin) deletes linewise > 3. `dx` (from mapping) deletes some characters > 4. `dVx` (from mapping) deletes some characters, but should delete > linewise ref: https://github.com/wellle/targets.vim/issues/214 ref: https://gitter.im/neovim/neovim?at=5b379ff7f1664406610e7483
Diffstat (limited to 'test/functional/lua/utility_functions_spec.lua')
0 files changed, 0 insertions, 0 deletions