My personal Nushell configuration, integration, and scripts.
Expected to be checked out to ~/.config/nushell and integrated as described in env.nu and config.nu (a single source statement respectively).
- Installed Starship
- Checked out nu_scripts inside this checked-out folder (community scripts)
nu_scripts checkout to nu_scripts
git clone --single-branch --depth 1 https://github.com/nushell/nu_scripts.git nu_scripts
Nushell runs through a compile and run step. (This is in contrast to other, more traditional and dynamic languages/shells.)
You can not source-include a nu file through a dynamically constructed path inside a nu file. Using ~ for home dir works, but not $'($basedir)/file.nu'.
The configuration is split into a two-step process: First, environment setup and configuration. Second, dynamic file paths can be prepared in the environment setup and then be source-included during configuration.
- Environment setup in
$nu.env-path - Configuration setup in
$nu.config-path
While using $env.APPDATA would be the technically correct place to put scripts and configuration, the default env.nu and config.nu files and defaults and new field introductions can change between Nushell versions.
The config reset command resets them to the (potentially new/updated) default.
The ~\AppData\Roaming\nushell subpathing is inconvenient. So this setup takes a ~/.config/nushell approach.