Mirrors/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell synced 2024-11-14 17:07:44 +00:00
Code Issues Projects Releases Packages Wiki Activity
fish-shell/tests/function.out

78 lines
2.2 KiB
Text
Raw Normal View History

use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
####################
# Test the -V flag
####################
# Testing -V
$foo: set in local scope, unexported, with 1 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$foo[1]: length=9 value=|local foo|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$foo: set in global scope, unexported, with 1 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$foo[1]: length=10 value=|global foo|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$foo: not set in universal scope
$bar: set in local scope, unexported, with 5 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$bar[1]: length=3 value=|one|
$bar[2]: length=8 value=|two 2|
$bar[3]: length=1 value=|\t|
$bar[4]: length=0 value=||
$bar[5]: length=1 value=|3|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$bar: set in global scope, unexported, with 5 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$bar[1]: length=3 value=|one|
$bar[2]: length=8 value=|two 2|
$bar[3]: length=1 value=|\t|
$bar[4]: length=0 value=||
$bar[5]: length=1 value=|3|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$bar: not set in universal scope
$baz: set in local scope, unexported, with 0 elements
$baz: set in global scope, unexported, with 0 elements
$baz: not set in universal scope
####################
# Testing -V with changed variables
$foo: set in local scope, unexported, with 1 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$foo[1]: length=9 value=|local foo|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$foo: set in global scope, unexported, with 1 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$foo[1]: length=10 value=|global foo|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$foo: not set in universal scope
$bar: set in local scope, unexported, with 5 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$bar[1]: length=3 value=|one|
$bar[2]: length=8 value=|two 2|
$bar[3]: length=1 value=|\t|
$bar[4]: length=0 value=||
$bar[5]: length=1 value=|3|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$bar: set in global scope, unexported, with 1 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$bar[1]: length=7 value=|bad bar|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$bar: not set in universal scope
$baz: set in local scope, unexported, with 0 elements
$baz: set in global scope, unexported, with 1 elements
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based.
2017-08-05 00:08:25 +00:00
$baz[1]: length=7 value=|bad baz|
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
$baz: not set in universal scope
Correctly handle mixing named arguments with function name Before this fix, `function -a arg1 name1` would produce a function named 'arg1'. After this fix, it will produce a function named 'name'. See #2068 for more.
2015-05-17 21:17:01 +00:00
Function name1 found
an invalid flag to `function` is handled wrong Specifically, an invalid flag keeps the function from being defined but does not emit an error message. Fixes #2827
2016-11-17 06:00:33 +00:00
Function name2 not found as expected
Correctly handle mixing named arguments with function name Before this fix, `function -a arg1 name1` would produce a function named 'arg1'. After this fix, it will produce a function named 'name'. See #2068 for more.
2015-05-17 21:17:01 +00:00
Function name3 found
an invalid flag to `function` is handled wrong Specifically, an invalid flag keeps the function from being defined but does not emit an error message. Fixes #2827
2016-11-17 06:00:33 +00:00
Function name4 not found as expected
use new `logmsg` and `set --show` in tests
2017-08-04 05:01:56 +00:00
####################
# Verify that functions can be copied. Tests against regression of issue #3601
####################
# Checking that the copied functions are identical other than the name
tests/functions: Don't compare diff output Turns out busybox diff (used on alpine) defaults to unified output, which we can't use because that prints filenames, and those are tempfiles made by psub. Instead, we use builtins to print the first line and compare the others.
2018-12-16 19:23:41 +00:00
function name1 --argument arg1 arg2
function name1a --argument arg1 arg2
1 = 1a
function name3 --argument arg1 arg2
function name3a --argument arg1 arg2
3 = 3a
Reserve some builtin names `argparse`, `read`, `set`, `status`, `test` and `[` now can't be used as function names anymore. This is because (except for `test` and `[`) there is no way to wrap these properly, so any function called that will be broken anyway. For `test` (and `[`), there is nothing that can be added and there have been confused users who created a function that then broke everything. Fixes #3000.
2018-02-25 18:25:29 +00:00
####################
# Checking reserved names
`functions -q`: Return false without an argument This erroneously listed functions and returned true.
2019-02-01 17:29:54 +00:00
####################
# Checking `functions -q` without arguments
False
Reference in a new issue Copy permalink