lacygoill
commented
4 years ago I think E523 is sometimes raised when you try to do something which is forbidden right now.
As a – contrived – example, consider this shell command:
vim -Nu NONE +'nno <expr> cd execute("wundo /tmp/undo")' /tmp/fileIt installs an <expr> mapping – triggered by the keysequence cd – which executes :wundo /tmp/undo. But if you press cd, E523 is raised, because this action is forbidden while textlock is active (see :h textlock).
Here, the solution is to refactor the mapping so that it's not defined with the <expr> argument:
vim -Nu NONE +'nno cd :wundo /tmp/undo<cr>' /tmp/fileNow pressing cd doesn't raise E523 anymore.
In the past, I had this error when one of my plugin was trying to execute :checktime while the buffer was modified and I was on the command-line. I can't reproduce anymore, so I don't know whether Vim's behavior has been changed by a patch, or the issue needs some other condition to be satisfied to be reproduced.
At the time, the solution that I found was to slightly delay the execution of :checktime via a timer.
I don't know whether it will help, but as a workaround, maybe you could try to delay the execution of :wundo, either via a timer:
call timer_start(0, {-> execute('wundo ...')})
^
increase the waiting time if neededOr via a one-shot autocmd listening to SafeState:
au SafeState * ++once wundo ...In both cases, you'll probably want a guard to make sure the active buffer is still the one you expect.
call timer_start(0, {-> expand('%:p') ==# 'my expected buffer' && execute('wundo ...')})
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
au SafeState * ++once if expand('%:p') ==# 'my expected buffer' | wundo ... | endif
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^The idea being that the state in which Vim is, and which currently forbids :wundo, will be over after a short time.
brammool
myitcv
Describe the bug
Very occasionally we see
E523: Not allowed here: wundoerrors in ourgovimtests. However we're struggling to understand how this corresponds to the docs forE523:Please can someone explain how
wundois connected toE523?We see this error in the context of
wundobeing executed bygovimwhich is a remote plugin if that is significant. The full error message looks like this:To Reproduce
We don't have repro steps; this is a very random and somewhat rare occurrence.
Expected behavior
Unclear; not sure why we are seeing the error.
Screenshots
n/a
Environment (please complete the following information):
Additional context Add any other context about the problem here.