traetox

Is there a work around that would allow for instantiating a new module? Module "types" don't work with `new` or `make`.

Even if we could figure out how to hook the new() function to allow for copying that environment, that would be cool too. I don't want to advocate for changing...

The var keyword being used to declare a new variable seems to mesh with the way normal types work. So thats my vote (if I get one). :) On Tue,...

Will do. Thank you! On Wed, Dec 4, 2019, 7:05 PM MichaelS11 wrote: > @traetox Please test > > — > You are receiving this because you were mentioned. >...

doesn't look like the PR fixed it. Here is a test script: ``` #!anko module Foo { var x = "testing" func bar1() { return x } func bar2(z) {...

ok, that seems entirely fair. I would say you could close this as "working as intended" Thank you for your time! We will poke a bit as we can on...

Throwing my vote in on getting this merged into v1. We are currently using this branch in our config library so that we can have both structured and dynamic elements...

Has there been any work on this? Are there any design docs or test code that outside parties could look at to start helping?

The PTY wasn't being closed when a client exited, check 4a2bef3ef52efb85953f3ea8b91c532b445212a0 It should clean things up.

HUGE +1 here. Selecting links, highlighting subsections, etc is very difficult in the Linux GUI. Would very much appreciate the right click and "Copy URL" option