> Also, I've tried to group all the commands in a single file, but
> without success. It seems they really need to be in different
> scripts, possibly in different contexts (legacy vs Vim9).
The location of the crash is where it's dealing with script-local
variables that were declared inside a block. So yes, the script matters
very much. Look out for any "var" inside a block.
> I forgot to mention that when Vim is started with the previous shell
> command, it gives these errors:
>
> Error detected while processing /home/user/.vim/plugin/fugitive.vim:
> line 2:
> E10: \ should be followed by /, ? or &
> line 3:
> E10: \ should be followed by /, ? or &
>
> Not sure why. I ignore them by pressing Enter.
This indicates line continuation with a backslash is used in compatible
mode. 'cpo' should be set to the Vim value.
> This in `~/.vim/plugged/vim-cmdline/plugin/cmdline.vim`:
>
> vim9
> au CmdlineLeave : timer_start(0, () => execute('au SafeState * ++once #'))
This should not have any effect. Does the crash still happen if you
remove this?
I don't see another hint, thus I hope you can find out more.
--
hundred-and-one symptoms of being an internet addict:
214. Your MCI "Circle of Friends" are all Hayes-compatible.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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/202101231138.10NBcXak2459691%40masaka.moolenaar.net.
