From 238a49b6f06b3b9ccac556f23686d149af3067f2 Mon Sep 17 00:00:00 2001 From: Kurtis Rader Date: Wed, 7 Jun 2017 17:05:50 -0700 Subject: [PATCH] document that `setenv` is now strict When 2.6.0 was released some people reported that the third-party `rbenv` and `pyenv` commands were incorrectly depending on our `setenv` function not behaving exactly like the csh command of the same name. Specifically, our version had a bug. It allowed more than one value. It no longer does so after it was rewritten so that the three auto-split vars were correctly handled. See issue #4103 --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index d8abee3e9..e1e7628f2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -43,6 +43,7 @@ If you are upgrading from version 2.5.0 or before, please also review the releas - `read` will read up to 10 MiB by default, leaving the target variable empty and exiting with status 122 if the line is too long. You can set a different limit with the `FISH_READ_BYTE_LIMIT` variable. - `read` supports a new `--silent` option to hide the characters typed (#838), for when reading sensitive data from the terminal. `read` also now accepts simple strings for the prompt (rather than scripts) with the new `-P` and `--prompt-str` options (#802). - `export` and `setenv` now understand colon-separated `PATH`, `CDPATH` and `MANPATH` variables. +- `setenv` is no longer a simple alias for `set -gx` and will complain, just like the csh version, if given more than one value (#4103). - `bind` supports a new `--list-modes` option (#3872). - `bg` will check all of its arguments before backgrounding any jobs; any invalid arguments will cause a failure, but non-existent (eg recently exited) jobs are ignored (#3909). - `funced` warns if the function being edited has not been modified (#3961).