From ed8dee04b61b7a2fc50589f58e6d4ccc47aca1ef Mon Sep 17 00:00:00 2001 From: Antoine Stevan <44101798+amtoine@users.noreply.github.com> Date: Wed, 18 Oct 2023 23:15:04 +0200 Subject: [PATCH] remove the last mention to `let-env` (#10718) # Description just caught a last mention to `let-env` in the `CONTRIBUTING.md` document :yum: # User-Facing Changes # Tests + Formatting # After Submitting --- crates/nu-std/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/nu-std/CONTRIBUTING.md b/crates/nu-std/CONTRIBUTING.md index f03f664c1..9108956a7 100644 --- a/crates/nu-std/CONTRIBUTING.md +++ b/crates/nu-std/CONTRIBUTING.md @@ -118,7 +118,7 @@ is described below: Use `export def` to make these names public to your users. * If your command is updating environment variables, you must use `export def --env` (instead of `export def`) to define the subcommand, - `export-env {}` to initialize the environment variables and `let-env` to + `export-env {}` to initialize the environment variables and `$env.VAR = val` to update them. For an example of a custom command which modifies environment variables, see: `./crates/nu-std/lib/dirs.nu`. For an example of a custom command which does *not* modify environment