All, I'm hitting an odd bug when I define an event which involves splitting a window. I've isolated it down to the following example:
autocmd CursorMoved * :execute ":silent! split /perl/module/mymod.pm" where mymod.pm is a valid perl module with valid perl syntax. In any case I have syntax coloring enabled for perl modules, yet when it hits a CursorMoved event it splits the window displaying the code but NOT coloring the syntax. When I run :hi it shows all of the highlighting configurations so I'm pretty sure it has something to do with the event combined with the execute action. Running: :syn on after the CursorMoved event happens is ignored. Anyways I'm running the latest 8.1 source - I tried it with a python module and a vimrc file and both hit the same issue. if there is a vim bug repo let me know and I'll file an official bug. thanks much, Ed (ps - one other bug - it looks like a split event triggered by CursorMoved at the very outset - right after the editor loads up - causes vim to freeze until an interrupt is given. ) -- -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/2da2485f-19c1-410c-b045-c723d386a109%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
