Jakub Žádník

You need to use a string interpolation to expand the -o string: `$"-o($env.DEPLOY_DIR)"`

More context and a potential solution outline: https://github.com/nushell/nushell/pull/6295#issuecomment-1221525223

After merging this PR https://github.com/nushell/nushell/pull/6257, `gh alias ` currently completes as an external completion if a) the external completion config is enabled AND b) the external completion returns non-empty result...

@jntrnr Can you give an example? I can't imagine what you mean.

There are two other cases where fall-through signatures would be useful: * `sudo`: Allow `sudo pacman` to reuse `pacman`'s signature. The `sudo` signature could be 100% fallthrough * `exec`: I...

@gotounix Just FYI, once this PR lands https://github.com/pypa/virtualenv/pull/2422 the virtualenv activation script will use the overlay system to activate the environment variables, so the `hide` or `hide-env` keywords won't be...

I don't think we should support cmd.exe built-ins because every shell has some built-ins. You can always do `bash -c ...` or `cmd /C ...`. If there is some functionality...

We do have plans for having some kind of package manager, nu_scripts is definitely not the long-term solution. Currently, we're focusing on improving the language, but packaging will be addressed...

We plan to change `source` to `source-env` which would be able to accept a dynamic path. But it would only preserve the environment. You won't be able to define commands...

Imagine `source foo.nu` as `#include "foo.h"` in C or `use some_mod::something` in Rust. That's essentially what it is. Nushell is a "compiled" language. You can do this, for example (`>`...