Hi, On Thu, May 9, 2024 at 1:16 AM Lifepillar <[email protected]> wrote: > > On 2024-05-09, Yegappan Lakshmanan <[email protected]> wrote: > > Hi, > > > > On Wed, May 8, 2024 at 2:11 PM Lifepillar <[email protected]> wrote: > >> > Looks like a bug. Should be able to do `foo.Config.option = true` > >> > >> Indeed. And fixed. That works with the latest Vim (9.1.399). > >> > > > > Yes. This should be addressed by patch 9.1.0398. If you see any > > additional problems > > in using different types of imported variables in a Vim9 script (after > > this patch), please > > open an issue. In particular, look for any issues in using nested types. > > Right now, the only issue I have is with autoload scripts in my vimrc, > but I see that it's being tracked as #13313 in GitHub. Other than that, > I must say that Vim 9 script has been rock solid for me (no more > crashes), and very pleasant to use! >
I have opened the PR https://github.com/vim/vim/pull/14740 to address this issue. Regards, Yegappan > > >> >> But how do I access the class member from the command line? Is that even > >> >> possible? > >> > >> I still haven't found a way to do that, and I'm starting to think that > >> it is not currently possible. If I put this in ~/.vim/autoload/foo.vim: > >> > > -- -- You received this message from the "vim_use" 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_use" 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_use/CAAW7x7nJHG36B%3Dspo2Xr0Y27FB7wDETn%2BV0p_PancBwtQN0Fmg%40mail.gmail.com.
