crates/nu-utils/src/default_files/README.md
default_env.nu:$env.config) that will be set during Nushell startup.env.nu.env.nu is also loaded. For example:
nuenv.nu via nu --env-config <path>nu -c <commandstring> or nu <script> startup so that ENV_CONVERSIONS is properly handled for Windows.no --no-config-file (-n).doc_env.nu.config env --default | nu-highlightdefault_config.nu:Counterpart to default_env.nu.
$env.config values that are not set via Rust defaults.env.nu.config.nu.config.nu is also loaded. For example:
nuconfig.nu via nu --config <path>config.nu would not be loaded. For example:
nu -n/--no-confignu -c "ls"nu <script.nu>doc_config.nu.color_config values are currently set in this file so that user's can introspect the valuescolor_config in nu-protocol::config and remove from default_config.nuconfig nu --default | nu-highlightdefault_config.nu (when all values are set via nu-protocol::config) will simply be:
$env.config = {}
doc_env.nuenv.nuconfig env --doc | nu-highlightconfig env --doc with help env.nu at some point.env.nudoc_config.nuCounterpart to doc_env.nu.
config.nuconfig nu --doc | nu-highlightconfig nu --doc with help config.nu at some point.config.nuscaffold_env.nu$nu.default-config-path directory does not exist, the directory is created and then both scaffold_env.nu and scaffold_config.nu are written to itconfig env command.scaffold_config.nuCounterpart to scaffold_env.nu.
$nu.default-config-path directory does not exist, the directory is created and then both scaffold_env.nu and scaffold_config.nu are written to itconfig nu command.