github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-11-24 21:31:18 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
97507a24a2
fish-shell/tests/test3.out

69 lines
1.1 KiB
Plaintext
Raw Normal View History

Add subdirectories darcs-hash:20050920133155-ac50b-9a14c6c664dd03afbe8e15e7c7998fcfb5c3c750.gz
2005-09-20 21:31:55 +08:00
Test 1 pass
Test 2 pass
Test 3 pass
Test 4 pass
Test 5 pass
Test 6 pass
Test 7 pass
Test 8 pass
Test 9 pass
Updates, bugfixing and minor edits on the test suite darcs-hash:20060605133133-ac50b-e2ee5868f9f3ede147c7059d90c0f520ed905a5f.gz
2006-06-05 21:31:33 +08:00
Test 10 pass
Fix for longstanding bug where set -e would fail to erase elements from an array. This was introduced in 7b3377e78c16b3ba74edb141ca0dd2ec895806b9
2012-05-10 16:04:18 +08:00
Test 11 pass
really fix bug in export status of universal vars; add tests for that bug
2012-12-30 02:25:00 +08:00
Test 12 pass
Test 13 pass
Test 14 pass
Test 15 pass
Properly fire events for universal variable changes Fixes #1929
2015-02-04 08:13:02 +08:00
Foo change detected
Foo change detected
harden test3 against undef vars This is only needed if we make undefined vars an error as proposed in issue #4163 but it's a good idea anyway.
2017-07-04 06:21:42 +08:00
count:5 content:[functionblock function global universal blocklocal]
really fix bug in export status of universal vars; add tests for that bug
2012-12-30 02:25:00 +08:00
Test 16 pass
Correctly un-export an env var when it is shadowed Prior to this fix, if you exported a variable in one scope and then unexported it in the next, it would remain exported. Example: set -gx VAR 1 function foo; set -l VAR; env; end foo Here 'VAR' would be exported to 'env' because we failed to notice that the env var is shadowed by an unexported variable. This occurred at env var computation time, not in env_set! Fixes #2132
2015-06-13 07:05:59 +08:00
__fish_test_env17=UNSHADOWED
SHADOWED
Test that exported vars remain exported I.e. the fix for #2611.
2017-06-21 22:53:50 +08:00
__fish_test_env17=UNSHADOWED
Test copying local-exported vars
2017-06-21 22:56:46 +08:00
wuwuwu
boo
wuwuwu
Comment and test that we shouldn't copy for blocks Seems important.
2017-06-22 17:11:12 +08:00
foo
bar
bar
Add test for issue 1526
2014-07-07 08:57:23 +08:00
Testing Universal Startup
1
1
2
2
harden test3 against undef vars This is only needed if we make undefined vars an error as proposed in issue #4163 but it's a good idea anyway.
2017-07-04 06:21:42 +08:00
testu undef in top level shell
testu undef in sub shell
Revert "Non-exported vars: rename SHLVL to shlvl" Duh, of course it is exported. This reverts commit 5fc17dcc826fd8fe7562c4b8293bff1e31472744.
2017-10-15 19:37:34 +08:00
SHLVL: 1
SHLVL: 2
SHLVL: 1
SHLVL: 1
SHLVL: 1
SHLVL: 4
SHLVL: 4
env.cpp: correctly check variable_can_be_array Closes #1746.
2014-10-08 09:51:49 +08:00
Elements in DISPLAY: 1
Export arrays as colon delimited, and support path-style variables This commit begins to bake in a notion of path-style variables. Prior to this fix, fish would export arrays as ASCII record separator delimited, except for a whitelist (PATH, CDPATH, MANPATH). This is surprising and awkward for other programs to deal with, and there's no way to get similar behavior for other variables like GOPATH or LD_LIBRARY_PATH. This commit does the following: 1. Exports all arrays as colon delimited strings, instead of RS. 2. Introduces a notion of "path variable." A path variable will be "colon-delimited" which means it gets colon-separated in quoted expansion, and automatically splits on colons. In this commit we only do the exporting part. Colons are not escaped in exporting; this is deliberate to support uses like `set -x PYTHONPATH "/foo:/bar"` which ought to work (and already do, we don't want to make a compat break here).
2018-09-10 09:32:15 +08:00
Elements in FOO and FOOPATH: 1 4
Change how arrays and environment variables interact. Prior to this change, inherited environment variables would be split on colons, becoming an array. This change eliminates that behavior. Now environment variables are always split on the record separator character (ASCII 0x1e), with the exception of a short whitelist of PATH, MANPATH, CDPATH. Likewise, exported variables are also exported delimited by rs, with the exception of the above whitelist. Fixes #1374, also see #1656
2014-10-13 06:01:35 +08:00
MANPATH=man1:man2:man3
Export arrays as colon delimited, and support path-style variables This commit begins to bake in a notion of path-style variables. Prior to this fix, fish would export arrays as ASCII record separator delimited, except for a whitelist (PATH, CDPATH, MANPATH). This is surprising and awkward for other programs to deal with, and there's no way to get similar behavior for other variables like GOPATH or LD_LIBRARY_PATH. This commit does the following: 1. Exports all arrays as colon delimited strings, instead of RS. 2. Introduces a notion of "path variable." A path variable will be "colon-delimited" which means it gets colon-separated in quoted expansion, and automatically splits on colons. In this commit we only do the exporting part. Colons are not escaped in exporting; this is deliberate to support uses like `set -x PYTHONPATH "/foo:/bar"` which ought to work (and already do, we don't want to make a compat break here).
2018-09-10 09:32:15 +08:00
DONT_ESCAPE_COLONS=1: 2: :3:
Join variables by their delimiter in quoted expansion This switches quoted expansion like "$foo" to use foo's delimiter instead of space. The delimiter is space for normal variables and colonf or path variables. Expansions like "$PATH" will now expand using ':'.
2018-10-01 07:34:01 +08:00
DONT_ESCAPE_SPACES=1 2 3 4
DONT_ESCAPE_COLONS_PATH=1::2:::3:
Allow setting universal path variables Support for path and unpath in universal variables. Fixes #5271
2018-10-22 15:49:09 +08:00
####################
# Path universal variables
Correctly split path environment variables about colons As noted in #5271
2018-10-28 06:20:32 +08:00
a b c 1:2:3 a b c 1 2 3
a b c 1 2 3 a b c 1 2 3
a:b:c 1 2 3 a b c 1 2 3
a:b:c 1:2:3 a b c 1 2 3
1:2:3 1 2 3
a:b a b
tests: add test for invalid variable name in for loop Work on #5800.
2019-04-09 20:10:51 +08:00
####################
# Variable names in other commands
Correct priority of universal and global variable setting When setting a variable without a specified scope, we should give priority to an existing local or global above an existing universal variable with the same name. In 16fd7804846c0aeca926f207eb0e2ae86f819931 there was a regression that made universal variables have priority. Fixes #5883
2019-05-26 08:15:50 +08:00
####################
# Global vs Universal Unspecified Scopes
global-vs-universal 1: universal
global-vs-universal 2: global
global-vs-universal 3: global2
global-vs-universal 4: universal
global-vs-universal 5:
Reference in New Issue Copy Permalink