History

Darren Schroeder ffde939df3 if --no-config-file(-n) is passed, do not load config files with -c (#9286 ) # Description I noticed recently these timing discrepancies. I was thinking they would be nearly identical but they were not. ``` > nu --no-std-lib -n -c "$nu.startup-time" 13ms 686µs 209ns > nu --no-std-lib -n > $nu.startup-time 2ms 520µs 416ns ``` My research showed that if `-n` was passed with `-c`, then the `-n` was essentially being ignored. This PR corrects that. Also worthy of understanding, if `nu -c "some command"` is passed, the default env file is always loaded. I believe that's on purpose so that a NU_LIB_DIRS env is available. ## After this PR (on a different system) ``` > nu --no-std-lib -n -c "$nu.startup-time" 6ms 688µs 600ns > nu -n --no-std-lib > $nu.startup-time 6ms 661µs 800ns ``` # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. -->		2023-05-25 08:24:56 -05:00
..
tests	Fix clippy warnings (upcoming) (#9282 )	2023-05-25 10:58:18 +12:00
command.rs	add `--ide-ast` for a simplistic ast for editors (#8995 )	2023-04-28 08:51:51 -05:00
config_files.rs	Fix warning on declared config variable that originates from commands (#8891 )	2023-04-26 09:21:51 -05:00
ide.rs	add `--ide-ast` for a simplistic ast for editors (#8995 )	2023-04-28 08:51:51 -05:00
logger.rs	Use variable names directly in the format strings (#7906 )	2023-01-29 19:37:54 -06:00
main.rs	Add virtual path abstraction layer (#9245 )	2023-05-23 23:48:50 +03:00
README.md	Remove old nushell/merge engine-q	2022-02-07 14:54:06 -05:00
run.rs	if --no-config-file(-n) is passed, do not load config files with -c (#9286 )	2023-05-25 08:24:56 -05:00
signals.rs	Cleanup of `src/main.rs` (#7801 )	2023-01-20 10:44:49 -08:00
terminal.rs	Move all functions of main.rs into modules (#7803 )	2023-01-20 13:20:38 -08:00
test_bins.rs	REFACTOR: move the banner from the `rust` source to the standard library (#8406 )	2023-05-10 07:05:01 -05:00
tests.rs	Parameter defaults to $nu.scope.commands (#9152 )	2023-05-11 13:59:56 -05:00

README.md

Nushell REPL

This directory contains the main Nushell REPL (read eval print loop) as part of the CLI portion of Nushell, which creates the nu binary itself.

Current versions of the nu binary will use the Nu argument parsing logic to parse the commandline arguments passed to nu, leaving the logic here to be a thin layer around what the core libraries.