about summary refs log tree commit diff
path: root/Test
Commit message (Collapse)AuthorAgeFilesLines
* 50089: unset LC_* for multibyte tests in X03zlebindkeyJun-ichi Takimoto2022-04-261-0/+1
|
* unposted (see 50072): check exit status in exit-from-trap testBart Schaefer2022-04-171-1/+1
|
* 50069: ChangeLog and test description for 50068Bart Schaefer2022-04-141-1/+1
|
* 50068: 'exit' in trap causes calling function to returnBart Schaefer2022-04-141-1/+1
|
* 50052: do nothing when skipping test V14systemJun-ichi Takimoto2022-04-141-1/+1
|
* 50046: ztst.zsh: export LANG to child zshJun-ichi Takimoto2022-04-141-0/+3
|
* 50013: skip %test if a chunk in %prep failsJun-ichi Takimoto2022-04-122-26/+31
| | | | | | Only %test is skipped if a chunk in %prep returns nonzero. Both %test and %clean are skipped if ZTST_unimplemented is set in a chunk of %prep. ZTST_cleanup is run in both cases.
* 49996 (Peter) + 50012: add ZTST_continueJun-ichi Takimoto2022-04-122-7/+28
|
* 50043: avoid spurious test failures when "make check" as rootBart Schaefer2022-04-112-3/+11
|
* 49906 (Bart), 49911: Fixes to querying jobs in subshell.Peter Stephenson2022-03-301-0/+28
| | | | | | | | Don't attempt to query invalid job off end of table, resulting in crashes from $jobtstates. If background task started in subshell, look at tatsks within subshell instead of main shell. Document and add test.
* 49813: Add missing testMikael Magnusson2022-03-301-1/+1
|
* 49910: move multibyte-related f-flagged test from E03 to D07Jun-ichi Takimoto2022-03-302-5/+12
| | | | | POSIX requires printf should calculate width/precision in %s conversion in bytes (not in characters) even in multibyte locale
* 49908: reset LC_CTYPE to C during testsJun-ichi Takimoto2022-03-301-2/+1
| | | | and do not export MODULE_PATH since child zsh will not import it
* 49853 + 49882/49883: make "${arr[*]:off}" compatible with ksh/bashJun-ichi Takimoto2022-03-291-0/+32
|
* 49802 (+49804): pass MODULE_PATH to zsh started in test W03Jun-ichi Takimoto2022-03-061-0/+1
|
* 49792: Non-interative shell input is line buffered.Peter Stephenson2022-03-031-0/+9
|
* 49787: test for jobs fix in 49783Peter Stephenson2022-03-032-0/+51
|
* 49518: fix exclusions for mixed - and + stacked optionsOliver Kiddle2021-12-141-0/+22
|
* 49628: Add an xfail test for RPS1/RPROMPT equivalence.Daniel Shahaf2021-12-011-0/+6
|
* 49624: Expect the test 'All identifiers are variable references in POSIX ↵Daniel Shahaf2021-12-011-1/+1
| | | | arithmetic' to pass, as it has been passing since 49611.
* 49601: don't create ambiguous history file entries for lines ending with a ↵Oliver Kiddle2021-11-281-0/+22
| | | | backslash
* 47599 (tweaked): New test for '{foo,bar}' in command positionDaniel Shahaf2021-11-261-0/+8
| | | | It's currently treated as a list but should perhaps be a brace expansion.
* github #82: Fix typosDimitris Apostolou2021-11-122-2/+2
|
* 49572: Let _expand preserve array form w/out zstyle globMarlon Richert2021-11-121-0/+11
|
* 49561: add zformat -F option, similar to -f but ternary expressions check ↵Oliver Kiddle2021-11-121-0/+24
| | | | for existence instead of doing math evaluation
* unposted (c.f. Bart: 49531): fix completion test where a typo marked it as ↵Oliver Kiddle2021-10-301-1/+1
| | | | expected to fail
* 49521: Define correct behavior of || completion matchersMarlon Richert2021-10-261-17/+109
| | | | | | | | * Add xfail tests to show how :||= matchers should behave in order to provide completion features that cannot be implemented with :|= matchers. * Update compwid.yo to further describe the correct behavior. * Update compwid.yo to use completion terminology more consistently.
* 49499 based on 49496 by Jun T.: fixes to option -A of _argumentsOliver Kiddle2021-10-231-0/+35
|
* 49456: clean up detection of private params in nested scopes, update docBart Schaefer2021-10-041-3/+3
|
* unposted: Fix typosDaniel Shahaf2021-09-262-2/+2
|
* 49353: Fix comments in sourced file.Peter Stephenson2021-09-091-0/+9
| | | | | | | | If the file was sourced from an interactive shell with INTERACTIVE_COMMENTS not set, comments were not parsed. Note there is a remaining edge case where the sourced file is in fact entered at the comment line.
* 49386: handle separate source/build treesBart Schaefer2021-09-081-1/+1
|
* 49377: fix segfault by 'bindkey -d' with reordered keymapnamtabJun-ichi Takimoto2021-09-081-0/+15
|
* 49218: run-help filters cmd_args before calling run-help-<command>Marlon Richert2021-09-061-0/+106
|
* 48888: improve doc for $$ and $PPID, add fail test for PPID readonly-nessBart Schaefer2021-09-061-0/+3
|
* 49269: Fix "[ ! -o ]".Peter Stephenson2021-08-101-1/+1
| | | | | This should detect "-o" as non-empty string; "-a" was alrady working. Update the test.
* 49166: fix coredump in ${name:offset:length} with ill-formatted lengthJun-ichi Takimoto2021-07-191-4/+3
|
* 48864: Improve extra-verbose completion display strings for array parameter ↵Marlon Richert2021-05-211-5/+9
| | | | values
* 48594 (plus an "F:" line corresponding to the question there): New tests for ↵Daniel Shahaf2021-05-181-0/+36
| | | | functions -t / functions -T
* 48560: add new test file missed on original commitBart Schaefer2021-05-151-0/+163
|
* 48810: fix potential name clash in test case for autoloadingBart Schaefer2021-05-151-2/+4
|
* 48787: Fix command status after failed ifPeter Stephenson2021-05-061-0/+5
| | | | | | | If "if" had a hard error in the condition, and there was no else clause, the command status was incorrectly cleared to zero. Add test.
* 48614: getopts: Calculate OPTIND according to POSIX_BUILTINSdana2021-05-031-0/+29
|
* 48606 + 48607 + unposted test: zmathfunc: Force arguments to be numbers and ↵Daniel Shahaf2021-04-211-1/+7
| | | | catch errors.
* unposted (cf. 48156): New test.Daniel Shahaf2021-04-211-0/+5
|
* 47704: POSIX export and readonly ignore "-p" when parameter names also appearBart Schaefer2021-04-181-5/+3
|
* 48560: add TYPESET_TO_UNSET option to remove initialization of parametersBart Schaefer2021-04-185-8/+28
| | | | | | | | | | Changes typeset such that ${newparam-notset} yields "notset" and "typeset -p newparam" does not show an assignment to the parameter. This is similar to the default behavior of bash and ksh, with minor differences in typeset output. Also add tests for some POSIX incompatibilities plus minor changes for test harness robustness.
* 48513: Let extra-verbose completion show parameter valuesMarlon Richert2021-04-161-1/+28
|
* unposted (cf. 48153): Add tests for max() and min().Daniel Shahaf2021-04-161-0/+24
|
* 47794: exec: run final pipeline command in a subshell in sh modebrian m. carlson2021-04-101-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | zsh typically runs the final command in a pipeline in the main shell instead of a subshell. However, POSIX specifies that all commands in a pipeline run in a subshell, but permits zsh's behavior as an extension. The default /bin/sh implementations on various Linux distros and the BSDs always use a subshell for all components of a pipeline. Since zsh may be used as /bin/sh in some cases (such as macOS Catalina), it makes sense to have the common sh behavior when emulating sh, so do that by checking for being the final item of a multi-item pipeline and creating a subshell in that case. From the comment above execpline(), we know the following: last1 is a flag that this command is the last command in a shell that is about to exit, so we can exec instead of forking. It gets passed all the way down to execcmd() which actually makes the decision. A 0 is always passed if the command is not the last in the pipeline. […] If last1 is zero but the command is at the end of a pipeline, we pass 2 down to execcmd(). So there are three cases to consider in this code: • last1 is 0, which means we are not at the end of a pipeline, in which case we should not change behavior. • last1 is 1, which means we are effectively running in a subshell, because nothing that happens due to the exec is going to affect the actual shell, since it will have been replaced. So there is nothing to do here. • last1 is 2, which means our command is at the end of the pipeline, so in sh mode we should create a subshell by forking. input is nonzero if the input to this process is a pipe that we've opened. At the end of a multi-stage pipeline, it will necessarily be nonzero. Note that several of the tests may appear bizarre, since most developers do not place useless variable assignments directly at the end of a pipeline. However, as the function tests demonstrate, there are cases where assignments may occur when a shell function is used at the end of a command. The remaining assignment tests simply test additional cases, such as the use of local, that would otherwise be untested.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-09 12:03:32 +0000