5 commits

Author	SHA1	Message	Date
Reilly Wood	80463d12fb	Revert "Primitives now use color closures..." (#7710) ... This temporarily reverts commit c5639cd9fa (PR https://github.com/nushell/nushell/pull/7650). See [here](https://github.com/nushell/nushell/pull/7650#issuecomment-1375036213) for details; the PR is accidentally adding ANSI escape codes to strings piped to externals. I think we should revert the PR because we're only 1-2 days away from a release; reverting it will give us more time to land+test a proper fix in the next release cycle.	2023-01-08 21:53:52 -08:00
Leon	c5639cd9fa	Primitives now use color closures when printed on the command line (#7650) ... # Description Closes #7554  # User-Facing Changes See above. # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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. Co-authored-by: Reilly Wood <26268125+rgwood@users.noreply.github.com>	2023-01-03 23:59:10 -08:00
Darren Schroeder	23ba01d89c	add performance metrics for measuring startup time (#3854) ... * add performance metrics for measureing startup time * removed some comments * update so tests pass * update default.toml for tests, merged main * fix clippy lints * wording changes	2021-07-29 18:52:40 -05:00
Andrés N. Robalino	1c941557c3	Remove unused help shell. Slight cleanup and improvement. (#3258)	2021-04-03 18:56:46 -05:00
Andrés N. Robalino	d2213d18fa	Playground infraestructure (tests, etc) additions. (#3179) ... * Playground infraestructure (tests, etc) additions. A few things to note: * Nu can be started with a custom configuration file (`nu --config-file /path/to/sample_config.toml`). Useful for mocking the configuration on test runs. * When given a custom configuration file Nu will save any changes to the file supplied appropiately. * The `$nu.config-path` variable either shows the default configuration file (or the custom one, if given) * We can now run end to end tests with finer grained control (currently, since this is baseline work, standard out) This will allow to check things like exit status, assert the contents with a format, etc) * Remove (for another PR)	2021-03-15 02:26:30 -05:00