Jakub Žádník

Ah, ok. Sure, that sounds cool, go ahead! One reason I'm using `conda` and not `virtualenv` is because it is more user-friendly. I think such an abstraction for `virtualenv` would...

One note, though. We're changing how `source` is going to work: It will be called `source-env` and would preserve only the environment, not custom commands and aliases. This will impact...

1. The `source-env` should be possible to land relatively soon, we plan it for the next release (3 weeks from now). Note that it will only source the environment variables,...

The `activate.nu` will be a module and you'll have to call `overlay add activate.nu`. Overlays support everything, including aliases so it will be possible to define the `deactivate` and `pydoc`....

One thing to take into account is that in `overlay remove ` the `` must be a static string. So you cannot call `overlay remove $name`, for example.

> hello there 👋 > > is there a plan or even a date for the `overlay` feature to be implemented on the `virtualenv` side? 😋 Yes, 27th of September...

I don't think completely bypassing parser errors like that is a good idea because it defeats the purpose of having custom signatures for externals and also ignores other errors unrelated...

Ah, sorry, check my latest message in the #completions channel on Discord, that explains it a bit. By "fall-through" signatures I mean you could type `def foo [..-rest] { }`...

This issue has come up often before, see the issues linked in this PR: https://github.com/nushell/nushell/pull/6567 We need to find a good solution to being able to relax the signature parsing.

I reproduced it on Linux, newest main built right now (ebc4694).