mirrors/zsh
1
0
Fork 0
mirror of git://git.code.sf.net/p/zsh/code synced 2025-06-17 21:18:06 +02:00
Code Releases Activity

53515: tests: correct ztst documentation error

Browse source
This commit is contained in:
dana 2025-04-27 07:47:53 -05:00
parent ad677029f8
commit 2601c19186
2 changed files with 11 additions and 9 deletions

6
ChangeLog
View file

@ -1,13 +1,15 @@
2025-04-27 dana <dana@dana.is>
* 53515: Test/B01cd.ztst: correct ztst documentation error
2025-04-20 Eric Cook <illua@users.sourceforge.net>
* unposted: Config/version.mk, Etc/FAQ.yo, NEWS, README: Test
release: zsh-5.9.0.2-test.
* 53463: Completion/Unix/Type/_hosts: allow overriding the default
matching control
2025-04-19 dana <dana@dana.is>
* 53483: Doc/Zsh/mod_zutil.yo, Src/Modules/zutil.c,

14
Test/B01cd.ztst
View file

@ -57,13 +57,13 @@
# subsequent whitespace being significant; lines are not subject to any
# substitution unless the `q' flag (see below) is set.
#
# Each line of a '>' and '?' chunk may be preceded by a '*', so the line
# starts '*>' or '*?'. This signifies that for any line with '*' in front
# the actual output should be pattern matched against the corresponding
# lines in the test output. Each line following '>' or '?' must be a
# valid pattern, so characters special to patterns such as parentheses
# must be quoted with a backslash. The EXTENDED_GLOB option is used for
# all such patterns.
# If any '>' or '?' line in a chunk is preceded by a '*', all lines in
# that chunk with the same symbol are pattern matched against the
# corresponding lines in the test output. For example, a '*>' anywhere
# in the chunk causes all other '>' lines to use pattern matching.
# Each line following '>' or '?' must be a valid pattern, so characters
# special to patterns such as parentheses must be quoted with a
# backslash. The EXTENDED_GLOB option is used for all such patterns.
#
# Each chunk of indented code is to be evaluated in one go and is to
# be followed by a line starting (in the first column) with