On Di, 17 Sep 2019, Paul Jolly wrote:
> This is great, thanks. I'm using state() and SafeStateAgain > (adding/removing the autocommand as required) > > I've got a WIP PR with the changes up at > https://github.com/govim/govim/pull/533 > > However one issue I'm seeing is that autocommands are not fired when > doing work in response to SafeStateAgain. The scenario looks like > this: > > 1. govim calls Vim with work to schedule > 2. Vim reports that it is not safe and so I add the work to a queue > and a callback to SafeStateAgain > 3. when safe, Vim fires the SafeStateAgain autocommand > 4. as part of this work, Vim calls back to govim with ch_evalexpr > 5. govim receives the message and calls back to Vim with a command to > open a file > 6. ... but not autocommands fire (whereas they did previously) > 7. the call from govim to Vim (5) returns > 8. the ch_evalexpr call from Vim to govim (4) returns > > Any ideas what might be going on here? Sounds like you need a nested somewhere. Have a look at `:h autocmd-nested` Best, Christian -- Jeder Mensch kann irren. Im Irrtum verharren wird jedoch nur der Tor. -- Marcus Tullius Cicero (106-43 v.Chr.) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20190917091744.GH30959%40256bit.org.
