fish-shell/tests/test3.out

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
Test 10 pass
Test 11 pass
Test 12 pass
Test 13 pass
Test 14 pass
Test 15 pass
Foo change detected
Foo change detected
count:5 content:[functionblock function global universal blocklocal]
Test 16 pass
__fish_test_env17=UNSHADOWED
SHADOWED
__fish_test_env17=UNSHADOWED
wuwuwu
boo
wuwuwu
Testing Universal Startup
1
1
2
2
testu undef in top level shell
testu undef in sub shell
SHLVL: 1
SHLVL: 2
SHLVL: 1
SHLVL: 1
SHLVL: 1
SHLVL: 4
SHLVL: 4
Elements in DISPLAY: 1
Elements in FOO: 4
MANPATH=man1:man2:man3
Add subdirectories darcs-hash:20050920133155-ac50b-9a14c6c664dd03afbe8e15e7c7998fcfb5c3c750.gz 2005-09-20 13:31:55 +00: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 13:31:33 +00: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 08:04:18 +00:00			`Test 11 pass`
really fix bug in export status of universal vars; add tests for that bug 2012-12-29 18:25:00 +00: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 00:13:02 +00: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-03 22:21:42 +00: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-29 18:25:00 +00: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-12 23:05:59 +00:00			`__fish_test_env17=UNSHADOWED`
			`SHADOWED`
Test that exported vars remain exported I.e. the fix for #2611. 2017-06-21 14:53:50 +00:00			`__fish_test_env17=UNSHADOWED`
Test copying local-exported vars 2017-06-21 14:56:46 +00:00			`wuwuwu`
			`boo`
			`wuwuwu`
Add test for issue 1526 2014-07-07 00:57:23 +00: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-03 22:21:42 +00:00			`testu undef in top level shell`
			`testu undef in sub shell`
Fix $SHLVL Due to being read-only, SHLVL wasn't being incremented properly for recursive invocations of fish. 2014-08-23 01:05:28 +00:00			`SHLVL: 1`
			`SHLVL: 2`
Decrement SHLVL when running `exec` `exec` removes fish from the shell "stack", so SHLVL needs to be decremented to match. This means `exec fish` will result in the same SHLVL in the new fish instance. Also tweak the SHLVL logic to interpret an environment SHLVL of "3foo" as garbage instead of as the value "3". Fixes #1693. 2014-09-20 00:31:34 +00:00			`SHLVL: 1`
			`SHLVL: 1`
			`SHLVL: 1`
			`SHLVL: 4`
			`SHLVL: 4`
env.cpp: correctly check variable_can_be_array Closes #1746. 2014-10-08 01:51:49 +00:00			`Elements in DISPLAY: 1`
Fix test breakage from 14724401f We can't use $PATHS to test the :-splitting because the global config file adds extra paths based on /etc/paths and /etc/paths.d. Ideally fish would have a way to suppress behavior like that, but for the time being it doesn't. 2014-10-08 02:37:13 +00:00			`Elements in FOO: 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-12 22:01:35 +00:00			`MANPATH=man1:man2:man3`