mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-05 11:01:13 +02:00
37205: update documentary comment
This commit is contained in:
parent
b33617e08b
commit
4e87006fc7
2 changed files with 11 additions and 7 deletions
|
@ -1,3 +1,7 @@
|
|||
2015-11-23 Barton E. Schaefer <schaefer@zsh.org>
|
||||
|
||||
* 37205: Test/B01cd.ztst: update documentary comment
|
||||
|
||||
2015-11-23 Peter Stephenson <p.stephenson@samsung.com>
|
||||
|
||||
* 37203: Src/params.c: WARN_CREATE_GLOBAL test in wrong place
|
||||
|
|
|
@ -57,13 +57,13 @@
|
|||
# subsequent whitespace being significant; lines are not subject to any
|
||||
# substitution unless the `q' flag (see below) is set.
|
||||
#
|
||||
# The first line (only) of a '>' and '?' chunk may be preceded by a '*',
|
||||
# so the line starts '*>' or '*?'. This signifies that all lines in the
|
||||
# chunk (not just the one with the '*' in front) in the actual output
|
||||
# are 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.
|
||||
# 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.
|
||||
#
|
||||
# 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
|
||||
|
|
Loading…
Reference in a new issue