History

Darren Schroeder d717e8faeb Add nu lib dirs default (#11248 ) # Description This PR is kind of two PRs in one because they were dependent on each other. PR1 - `3de58d4dc2` with update `7fcdb242d9` - This follows our mantra of having everything with defaults written in nushell rust code. So, that if you run without a config, you get the same behavior as with the default config/env files. This sets NU_LIB_DIRS to $nu.config-path/scripts and sets NU_PLUGIN_DIRS to $nu.config-path/plugins. PR2 - `0e8ac876fd` - The benchmarks have been broke for some time and we didn't notice it. This PR fixes that. It's dependent on PR1 because it was throwing errors because PWD needed to be set to a valid folder and `$nu` did not exist based on how the benchmark was setup. I've tested the benchmarks and they run without error now and I've also launched nushell as `nu -n --no-std-lib` and the env vars exist. closes #11236 # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` 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-12-07 08:13:50 -06:00
..
tests	Spread operator in record literals (#11144 )	2023-11-29 18:31:31 +01:00
command.rs	Apply nightly clippy fixes (#11083 )	2023-11-17 09:15:55 -06:00
config_files.rs	Improve case insensitivity consistency (#10884 )	2023-11-08 23:58:54 +01:00
ide.rs	Convert FileNotFoundCustom to named fields (#11123 )	2023-11-21 17:30:21 -06:00
logger.rs	Use variable names directly in the format strings (#7906 )	2023-01-29 19:37:54 -06:00
main.rs	Add nu lib dirs default (#11248 )	2023-12-07 08:13:50 -06:00
README.md	Remove old nushell/merge engine-q	2022-02-07 14:54:06 -05:00
run.rs	allow `--login` to be used with nu's `--commands` parameter (#10253 )	2023-09-06 13:27:16 -05:00
signals.rs	Cleanup of `src/main.rs` (#7801 )	2023-01-20 10:44:49 -08:00
terminal.rs	Fix `rm` on macOS (#10282 )	2023-09-08 19:03:30 -05:00
test_bins.rs	add echo_env_mixed testbin to reduce windows only tests (#11172 )	2023-11-28 06:42:35 -06:00
tests.rs	Spread operator for list literals (#11006 )	2023-11-22 23:10:08 +02: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.