On Sat, Jan 15, 2022 at 1:25 PM Doug Kearns wrote:
>
> On Thu, 13 Jan 2022 at 04:55, Manuel Ortega wrote:
>
> > Ah, it seems I misremembered the details. But my point remains pretty much
> > the same. I'd said it was unexpected for the comment char of vim9script to
> > be '#'; it's at least
On Thu, 13 Jan 2022 at 04:55, Manuel Ortega wrote:
> Ah, it seems I misremembered the details. But my point remains pretty much
> the same. I'd said it was unexpected for the comment char of vim9script to
> be '#'; it's at least as unexpected for it to be '#', and even
> more unexpected for
Manuel Ortega wrote:
> > Manuel Ortega wrote:
> >
> > > I very much hope that one thing will be changed. Currently '#' only
> > starts
> > > a comment when it's followed by a space, if I understand correctly.
> > Please
> > > make it instead behave like almost every other language that
On Friday, January 7, 2022 at 2:01:49 PM UTC-6 Bram Moolenaar wrote:
>
> Manuel Ortega wrote:
>
> > I very much hope that one thing will be changed. Currently '#' only
> starts
> > a comment when it's followed by a space, if I understand correctly.
> Please
> > make it instead behave like
Manuel Ortega wrote:
> I very much hope that one thing will be changed. Currently '#' only starts
> a comment when it's followed by a space, if I understand correctly. Please
> make it instead behave like almost every other language that uses '#' as a
> comment character, and *don't*
I very much hope that one thing will be changed. Currently '#' only starts
a comment when it's followed by a space, if I understand correctly. Please
make it instead behave like almost every other language that uses '#' as a
comment character, and *don't* require that it be followed by a
Bram, Thank you for all the hard work you do. I think the choices you’ve
made have been good trade-offs. You are a superstar!
On Thursday, December 30, 2021 at 3:39:55 PM UTC-5 Bram Moolenaar wrote:
>
> [it appears this message did not reach the list, sending it again]
>
> The work on Vim9
* Bram Moolenaar [220104 12:26]:
> Marvin Renich wrote:
> > * Bram Moolenaar [220103 12:33]:
[snip]
> > I agree that using the (cleansed) file name is suboptimal, but it was
> > the simplest choice. There are a couple other possibilities. One is to
> > require the "as" clause.
[snip]
> > Every
Marvin Renich wrote:
> * Bram Moolenaar [220103 12:33]:
> > > On 2022-01-03, Marvin Renich wrote:
> > > > Don't bother with the
> > >
> > > > import MyClass from "myclass.vim"
> > > > import {someValue, MyClass} from "thatscript.vim"
> > > >
> > > > syntax, and only provide
> > > >
> > >
* Bram Moolenaar [220103 12:33]:
> > On 2022-01-03, Marvin Renich wrote:
> > > Don't bother with the
> >
> > > import MyClass from "myclass.vim"
> > > import {someValue, MyClass} from "thatscript.vim"
> > >
> > > syntax, and only provide
> > >
> > > import "myclass.vim"
> > > import
> On 2022-01-03, Marvin Renich wrote:
> > Don't bother with the
>
> > import MyClass from "myclass.vim"
> > import {someValue, MyClass} from "thatscript.vim"
> >
> > syntax, and only provide
> >
> > import "myclass.vim"
> > import "myclass.vim" as Other
> >
> > and require use of the
Marvin Renich wrote:
> * Bram Moolenaar [220103 07:07]:
> >
> > > On 2021-12-30, Bram Moolenaar wrote:
> > > > If you have remarks on something in Vim9 script that you think should be
> > > > different, speak up now! Soon we'll only make backwards compatible
> > > > changes to avoid
* Bram Moolenaar [220103 07:07]:
>
> > On 2021-12-30, Bram Moolenaar wrote:
> > > If you have remarks on something in Vim9 script that you think should be
> > > different, speak up now! Soon we'll only make backwards compatible
> > > changes to avoid breaking existing plugins.
> >
> > There
> ["Followup-To:" header set to gmane.editors.vim.]
> On 2021-12-30, Bram Moolenaar wrote:
> > The work on Vim9 script is coming to a point where the syntax and
> > semantics are practially done. There might be some more tests
> > uncovering problems that need to be fixed and perhaps some tiny
fair enough, thanks.
在2021年12月31日星期五 UTC+8 19:35:37 写道：
>
> Wei Zhang wrote:
>
> > any chance to remove the space compulsory in vim9 ??
> >
> > Vim9 script enforces proper use of white space. This is no longer
> allowed:
> > >
> > var name=234 # Error!
> > var name= 234 # Error!
> > var name
Wei Zhang wrote:
> any chance to remove the space compulsory in vim9 ??
>
> Vim9 script enforces proper use of white space. This is no longer allowed:
> >
> var name=234# Error!
> var name= 234# Error!
> var name =234# Error!
> There must be
any chance to remove the space compulsory in vim9 ??
Vim9 script enforces proper use of white space. This is no longer allowed:
>
var name=234# Error!
var name= 234# Error!
var name =234# Error!
There must be white space before and after the "=":
[it appears this message did not reach the list, sending it again]
The work on Vim9 script is coming to a point where the syntax and
semantics are practially done. There might be some more tests
uncovering problems that need to be fixed and perhaps some tiny tweaks,
but otherwise it has been
18 matches
Mail list logo
