The idea sounds good, but the syntax proposal feels somewhat confusing. There’s definitely an environment… many environments in fact. So it’s completely unclear what no-environment would mean in this case. Also, the wrappers as I understand it are richer than just the environment. The proposal by @mvo seems to imply that we’d want those gone for real once the flag is used.
It also seems like “wrapper” is not a good term for this idea, so these other suggestions don’t sound great either. The problem with wrapper is that it doesn’t explain properly the multi-purpose idea explained above. In other words, the point is not to wrap… that’s just how we implemented it. The point is to prepare the environment for the application to be run.
Here is a proposal that takes those ideas into account:
For now, this would only accept the values “none”, and “”, with the latter being the default and implying the current behavior. The former disables the wrapping altogether, including the environment. With these two settings, down the road we can evolve to support “environment”, which would adapt only the environment, and some other settings as we learn a bit more about these issues.
How does that sound?