Jakub Žádník

Ah, I didn't know it's regex by default. IMO it should be plain string instead of regex by default. I'll change the issue description. Thanks for looking into it @bobhy!

I can't reproduce the issue because `alias = foo_bar baz` is not a valid syntax. Seems like you meant `alias foo_bar = baz` which indeed crashes Nushell. We're currently figuring...

@charleschege Can you please open a new issue with the environment shorthand issue?

@fdncred What is the output of your `overlay list` at the time you're calling the `hide-env`?

Yeah, it might be the inherited env vars... I thought it had to do with multiple overlays but couldn't reproduce it and since you have only one, the problem will...

What is `truecolor`?

You can run file starting with - (the quoting style depends on which shell you use, Nushell auto-strips quotes, so you need to double-quote): ``` nu `'-foo.nu'` ``` I guess...

FWIW, currently, we support `extern-wrapped` which converts all its positional parameters to strings, so you can pass unknown flags or filenames starting with `-` and they all will be strings.

One thing we might consider is `use-env` or `use --env` to _only_ run the `export-env` block of a module without bringing in any parser definitions.

We could strip ansi sequences for `touch` and other "sink" commands that do not pass data further. But the metadata approach could be a good fit as well.