Darren Schroeder
Darren Schroeder
I wouldn't worry about categories too much, they can change pretty easily. - `custom` are `custom commands` like `def blah [] {}` - `keyword` are usually created in the nushell...
`let-env` and `regsiter` aren't commands anymore. `do`, `error make`, `hide-env` are still there in category core as type built-in. Having said that, I'm not surprised of some inconsistencies.
I guess your proposal means that if a user has a config.nu or env.nu it's additive and specifically meant to change a default. This is similar to people today using...
I think `nu -c` only loads the env.nu file. I don't believe it loads the config.nu.
I'm not sure you can depend on env.nu being slower thought. For instance, my config.nu is much bigger and i do a lot of `use`ing and `source`ing at the end...
As discussed on discord and other places, it's probably important to understand what we want loaded when each parameter is passed into nushell. I created this [gist](https://gist.github.com/fdncred/b87b784f04984dc31a150baed9ad2447/) to demonstrate how...
How does this PR work on non-zero exit codes that are not errors like mentioned here https://www.sophiajt.com/exit-codes/?
I'm ok with this PR as long as I don't get an error every time I run `git log` and similar commands that return non-zero exit codes when there isn't...
https://github.com/nushell/nushell/pull/13873 needs to be cleaned up for `false` to happen in the next release.
Have we worked through the issues here? Are we ready to land?