> > In Vim9, such a confusing error would not occur for 2 reasons:
>
> Which is why I hope at some point we'll have a 'vim9cmdline' option to
> let us use all the Vim9 syntaxes on the command-line. Sometimes,
> while developing a plugin, we need to execute a few commands on the
> command-line; if we're writing a plugin in Vim9 stript, it's confusing
> to have to use a legacy syntax.
We could use ":vim9" as a command modifier. Although it might be
confusing to use the same at script level as with a command modifier.
Using "vim9cmd" and "vim9script" works, and we could use "vim9" as the
short form of "vim9cmd", since it's not so bad putting "vim9script" at
the top of a script, you only type it once.
Shorter forms such as "v9" and "vi9" don't work, these match existing
commands and they would be used in legacy script context.
--
FATHER: Who are you?
PRINCE: I'm ... your son ...
FATHER: Not you.
LAUNCELOT: I'm ... er ... Sir Launcelot, sir.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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/202102061233.116CX7tD2553082%40masaka.moolenaar.net.
