Yes, but this does not work for a nested def function. Setting one of these
options to a funcref stringifies the funcref and then later unstringifies
the value to get back to a callback. This process loses the environment
bound in the closure causing an E1248.
On Tuesday, January 24, 2023 at
On Di, 24 Jan 2023, Ernie Rael wrote:
> I'm just updating to v6.0 u-ctags. I haven't tried using ctags/tags on
> vim9script.
>
> Wondering how well that works, any suggestions on getting a good tags file
> for vim9script?
>
> ":help ctags" doesn't list a program that's good for vim9script ;-)
Hi,
On Tue, Jan 24, 2023 at 7:12 PM Geoff Reedy
wrote:
> I think it would be neat to allow a funcref in autocmd_add and add a
> callback_T cmd_cb field to the auto command struct for it.
>
> The same would be nice for options like omnifunc. Interestingly these are
> stored into the buffer
Bram Moolenaar wrote:
> Currently I decided to keep it relatively simple and only provide three
> ways:
>
> - public: read and write access, using the "public" keyword
> - default: read access only, no keyword used
> - private: name prefixed with an underscore
It can be fine, but:
- it's not
I'm just updating to v6.0 u-ctags. I haven't tried using ctags/tags on
vim9script.
Wondering how well that works, any suggestions on getting a good tags
file for vim9script?
":help ctags" doesn't list a program that's good for vim9script ;-)
-ernie
--
--
You received this message from the
On 23/01/23 4:53 AM, Bram Moolenaar wrote:
I expected a lively discussion about alternatives for the class
implementation, but nothing much happened. Does this mean that most
people agree with making this changed:
1. Make object members public by default. They can be read and written
from
Doub Kearns wrote:
> I'm a bit short on time today but I have a few thoughts, some of which may
> be partially reiterated from the previous related thread, to keep the ball
> rolling.
Thanks for your opinions. I'll take them into account.
> = Underscore for Private Access =
>
> The current
On Mon, 23 Jan 2023 at 23:53, Bram Moolenaar wrote:
>
> I expected a lively discussion about alternatives for the class
> implementation, but nothing much happened.
Some of us are old soldiers with too many scars. :)
I'm a bit short on time today but I have a few thoughts, some of which may
be
Patch 9.0.1240
Problem:Cannot access a private object member in a lambda defined inside
the class.
Solution: Go up the context stack to find the class. (closes #11866)
Files: src/vim9expr.c, src/vim9class.c, src/proto/vim9class.pro,
Patch 9.0.1239
Problem:Cannot have a line break before an object member access.
Solution: Check for "." in next line. (closes #11864)
Files: src/eval.c, src/testdir/test_vim9_class.vim
*** ../vim-9.0.1238/src/eval.c 2023-01-11 19:11:09.468757611 +
--- src/eval.c 2023-01-24
Patch 9.0.1238
Problem::runtime completion can be further improved.
Solution: Also complete the {where} argument values and adjust the
completion for that. (closes #11874)
Files: runtime/doc/builtin.txt, src/cmdexpand.c,
src/proto/scriptfile.pro,
11 matches
Mail list logo
