any way to trigger CursorMoved in a test?

[justinmk]

From what I can tell after reading docs/web, cursor movement in a script or macro, such as Vader, does not trigger the CursorMoved event. :help CursorMoved actually says something briefly on this:

Not triggered when there is typeahead or when an operator is pending.

So testing effects of a CursorMoved autocmd in Vader seems impossible, but hopefully I'm wrong. I've tried breaking up the moving in separate normal commands, and even tried things like this:

Execute (visual mode forwards):
  normal vwjs42
  call inputsave()
  normal ll
  Assert !exists("#SneakPlugin#CursorMoved#<buffer>")
  call inputrestore()
  normal os55;d

Since inputsave() clears the "typeahead", I was hopeing this would allow the test to trigger CursorMoved. But it doesn't.

You can verify the general problem with these commands:

au CursorMoved * echo 'hi'
normal lh

"hi" is not echoed, though if the user typed lh in normal mode, it would be echoed.

Any ideas? I will ping the vim_use mailing list too.

Thanks!

[junegunn]

Hmm, I wasn't aware of the issue, but it seems to be the case and I have no idea if it's possible to change the behavior. Given that, I guess the only way we can test CursorMoved event is to manually trigger it with doautocmd within the test 😕

Execute (setup):
  let g:cnt = 0
  augroup CursorMovedTest
    autocmd!
    autocmd CursorMoved * let g:cnt += 1
  augroup END

Given:
  hello world

Do:
  llllx
  :doautocmd CursorMoved\<CR>

Expect:
  hell world

Execute (cleanup):
  " 1 not 5 :/
  AssertEqual 1, g:cnt
  augroup CursorMovedTest
    autocmd!
  augroup END
  augroup! CursorMovedTest

[justinmk]

doautocmd is good enough, thanks! I didn't know that existed.

[blueyed]

Just for reference: this is not possible to test in Vader, because CursorMoved (and also TextChanged) are checked/emitted in the main loop, which is not used when using +Vader.

Vim itself does not appear to have any tests for CursorMoved, and only a single test for TextChanged (via the terminal, https://github.com/vim/vim/blob/f3ba14ffd32faa1856a99cf657c426bf9d1204ae/src/testdir/test_autocmd.vim#L1310-L1329).

Reminded me of #124, where (Neo)Vim wrapped in tmux could be used for tests like these.

But then it might be better to add support to Vim/Neovim for triggering a main loop iteration / autocommands check manually (via some option, so it would not be necessary to have an equivalent of doautocmd in tests).

[justinmk]

so it would not be necessary to have an equivalent of doautocmd in tests

Is that really different than manually triggering the event loop? :)

[blueyed]

What I've meant was that you could set an option in test/vimrc which would trigger the event-checking part of the main loop after each command in a script (automatically).
This adds overhead however, so it seems still better to explicitly trigger those autocommands in tests then.

Took me a while to figure this out however.
I've tried to use -s (scriptin) then, which actually triggers the main loop, but only once.
Next step would be -e (exmode), but similar to -s this would require to have the commands in tests to be passed in there separately, and not just call :Vader.