From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16290 invoked from network); 22 Sep 2021 22:42:37 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 22 Sep 2021 22:42:37 -0000 ARC-Seal: i=1; cv=none; a=rsa-sha256; d=zsh.org; s=rsa-20210803; t=1632350557; b=lkldAKM//l5Bz3g0RCrLfwfuH+CcH9K6g8xSKFKG+TiL1vnwLBpV1/4iNTNKwhZjI1tGjB8Pqt PWR42fxcYcFKVgJS9Qou4EGpx4ArApdxqVmYvL608JcJu+pcZzp2cCXlL9pfdlEmJocMEI8QmC xmW4/1+8En0Qbn+N/3QS2QdcJiVFZui1nZ1xObFobHYqQpF9J9uoGogU2AfO7BDzRMtuifV3K0 HVE9uCf1Ugrq70h1gXWcajKcVhOqNqqeDBEaltYXivq1cZRrDy1SkxUoV2fCaeSyecyDipakSp zkxywZdhbybiZwGuwo7nkwmYoWyApASlt02fjBRS/gyDQQ==; ARC-Authentication-Results: i=1; zsh.org; iprev=pass (forward101o.mail.yandex.net) smtp.remote-ip=37.140.190.181; dkim=pass header.d=ratijas.tk header.s=mail header.a=rsa-sha256; dmarc=none header.from=ratijas.tk; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed; d=zsh.org; s=rsa-20210803; t=1632350557; bh=PWSM4NPUmGGIyaEYszEmBRXQpZQrLwjk45DrzFV4p+0=; h=List-Archive:List-Owner:List-Post:List-Unsubscribe:List-Subscribe:List-Help: List-Id:Sender:Content-Transfer-Encoding:MIME-Version:Message-ID:Date: Subject:Cc:To:From:DKIM-Signature:DKIM-Signature; b=ULA9bFSvIG9Qad8Bh5Wj9BJkaoWQ6KfYXRGDyuLXzQaDDRpPVvhZtnqviLlpRcpcP3HEtXYk6W 0TW/+bUtrhq1qAdEcTwrdB04vcuP4L3yvUq4djy189q4BQNxW3ofj14z45KBb4juOi505jjWo6 rylHubZHsZDSpd3VLpwbiJ8wiw/mskc8XeU32OlO1nPbRnCS2/w2I6etCe23o6dXkHkkXapf1+ zsIQHrZfkRPYOqWsBuDLbaWp89+IZa8+vYBJvrXxSyvwkVDQmWsESbkHPhndC9KcYHPzCooDcf pAgSP5zIiJL3oSBCCb4F+x266zg3DxdwK6rP6pHDmUHK9g==; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20210803; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Content-Transfer-Encoding: MIME-Version:Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-Type: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References; bh=3KJMI4AGi5FOs9ss4sEY5VbudCgHRREHOkXYA/gXvAY=; b=Grpm7ZQ/n3HwGMVPEMFKduzrXs +5ezipz5NAzNuFfGS0pr9p+axVjaKIHUA71JAu70oWfXZqZFVyvKDq9n23BlDatudjXKXYP59Bo6Y /4mvqa8pNvgmTTV/jJSJv4m9JgoCNjJ78B8UcWBC5tEAjGYsVmC7xDDg+EPRXqnxiaDk4UJfe5fan Szx/fFGNbY9RpJZREjff+wB4zFphWLTvve9k87fkENlmWf5yPdMrnaGHDHtPf5/VixwcsNXWGgRLo mljMgihj45EVTe8iTQAZyJj//JjUqORC4pL8z/M7igJvyVVE+9MtnOENgMlSvxYXoQroxbNXawCBC zYbwE90Q==; Received: from authenticated user by zero.zsh.org with local id 1mTAwl-000NzH-Os; Wed, 22 Sep 2021 22:42:35 +0000 Authentication-Results: zsh.org; iprev=pass (forward101o.mail.yandex.net) smtp.remote-ip=37.140.190.181; dkim=pass header.d=ratijas.tk header.s=mail header.a=rsa-sha256; dmarc=none header.from=ratijas.tk; arc=none Received: from forward101o.mail.yandex.net ([37.140.190.181]:47350) by zero.zsh.org with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1mT9cM-000KPY-OT; Wed, 22 Sep 2021 21:17:28 +0000 Received: from myt5-1ce284ea94ec.qloud-c.yandex.net (myt5-1ce284ea94ec.qloud-c.yandex.net [IPv6:2a02:6b8:c12:4d97:0:640:1ce2:84ea]) by forward101o.mail.yandex.net (Yandex) with ESMTP id 4656E369DF4F for ; Thu, 23 Sep 2021 00:17:25 +0300 (MSK) Received: from myt6-efff10c3476a.qloud-c.yandex.net (myt6-efff10c3476a.qloud-c.yandex.net [2a02:6b8:c12:13a3:0:640:efff:10c3]) by myt5-1ce284ea94ec.qloud-c.yandex.net (mxback/Yandex) with ESMTP id 9AbgVMuQV3-HOEi2cXv; Thu, 23 Sep 2021 00:17:25 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratijas.tk; s=mail; t=1632345445; bh=3KJMI4AGi5FOs9ss4sEY5VbudCgHRREHOkXYA/gXvAY=; h=Message-Id:Date:Subject:To:From:Cc; b=Xa16sFBugWlNTkYW+VTYkwB0GBnq6T10Ifc7v1nvcMvvVgeqKQyca0ipz25MCXNpX ivL07BpMws/+olVPi0UUCTAi4Y2+Kho4gY+J5+aGyvuxhB5SJaVm4mt/AEB2hIaX9c KaViTV49Heee5VzCCMhSY5GlDfiBMDjJsgGwa+P4= Authentication-Results: myt5-1ce284ea94ec.qloud-c.yandex.net; dkim=pass header.i=@ratijas.tk Received: by myt6-efff10c3476a.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id y7L06NGeqb-HOFiQIDo; Thu, 23 Sep 2021 00:17:24 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) From: ivan tkachenko To: zsh-workers@zsh.org Cc: ivan tkachenko Subject: [PATCH 1/2] cosmit: Remove trailing whitespaces in expn.yo Date: Thu, 23 Sep 2021 00:17:18 +0300 Message-Id: <20210922211719.39806-1-me@ratijas.tk> X-Mailer: git-send-email 2.33.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Validation-by: larryv@zsh.org X-Seq: 49435 Archived-At: X-Loop: zsh-workers@zsh.org Errors-To: zsh-workers-owner@zsh.org Precedence: list Precedence: bulk Sender: zsh-workers-request@zsh.org X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: --- Doc/Zsh/expn.yo | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/Doc/Zsh/expn.yo b/Doc/Zsh/expn.yo index c218ded05..eea147bde 100644 --- a/Doc/Zsh/expn.yo +++ b/Doc/Zsh/expn.yo @@ -84,7 +84,7 @@ vindex(histchars, use of) A history expansion begins with the first character of the tt(histchars) parameter, which is `tt(!)' by default, and may occur anywhere on the command line, including inside double quotes (but not inside single quotes -tt('...') or C-style quotes tt($'...') nor when escaped with a backslash). +tt('...') or C-style quotes tt($'...') nor when escaped with a backslash). The first character is followed by an optional event designator (ifzman(see )noderef(Event Designators)) and then an optional word @@ -496,7 +496,7 @@ which treats var(arg) as a file name and replaces it with the file's contents. The tt(=) form is useful as both the tt(/dev/fd) and the named pipe -implementation of tt( >LPAR())var(process1)tt(RPAR() > >LPAR())var(process2)tt(RPAR())) The shell uses pipes instead of FIFOs to implement the latter @@ -974,7 +974,7 @@ If the tt(MULTIBYTE) option is set and the number is greater than 127 ) item(tt(%))( Expand all tt(%) escapes in the resulting words in the same way as in -prompts (see +prompts (see ifzman(EXPANSION OF PROMPT SEQUENCES in zmanref(zshmisc))\ ifnzman(noderef(Prompt Expansion))). If this flag is given twice, full prompt expansion is done on the resulting words, depending on the @@ -1729,7 +1729,7 @@ This produces the result tt(b). First, the inner substitution tt("${foo}"), which has no array (tt(@)) flag, produces a single word result tt("bar baz"). The outer substitution tt("${(@)...[1]}") detects that this is a scalar, so that (despite the `tt((@))' flag) the subscript -picks the first character. +picks the first character. ) item(tt("${${(@)foo}[1]}"))( This produces the result `tt(bar)'. In this case, the inner substitution @@ -1763,7 +1763,7 @@ sect(Command Substitution) cindex(command substitution) cindex(substitution, command) A command enclosed in parentheses preceded by a dollar sign, like -`tt($LPAR())...tt(RPAR())', or quoted with grave +`tt($LPAR())...tt(RPAR())', or quoted with grave accents, like `tt(`)...tt(`)', is replaced with its standard output, with any trailing newlines deleted. If the substitution is not enclosed in double quotes, the @@ -2461,7 +2461,7 @@ qualifiers are also not applied in ordinary pattern matching. ) item(tt(u))( Respect the current locale in determining the presence of multibyte -characters in a pattern, provided the shell was compiled with +characters in a pattern, provided the shell was compiled with tt(MULTIBYTE_SUPPORT). This overrides the tt(MULTIBYTE) option; the default behaviour is taken from the option. Compare tt(U). (Mnemonic: typically multibyte characters are from Unicode in the UTF-8 @@ -2712,18 +2712,18 @@ expected, if combined with a `tt(=)', the value given must match the file-modes exactly, with a `tt(PLUS())', at least the bits in the given number must be set in the file-modes, and with a `tt(-)', the bits in the number must not be set. Giving a `tt(?)' instead of a -octal digit anywhere in the number ensures that the corresponding bits +octal digit anywhere in the number ensures that the corresponding bits in the file-modes are not checked, this is only useful in combination with `tt(=)'. If the qualifier `tt(f)' is followed by any other character anything -up to the next matching character (`tt([)', `tt({)', and `tt(<)' match +up to the next matching character (`tt([)', `tt({)', and `tt(<)' match `tt(])', `tt(})', and `tt(>)' respectively, any other character matches itself) is taken as a list of comma-separated var(sub-spec)s. Each var(sub-spec) may be either an octal number as described above or a list of any of the characters `tt(u)', `tt(g)', `tt(o)', and `tt(a)', followed by a `tt(=)', a `tt(PLUS())', or a -`tt(-)', followed by a list of any of the characters `tt(r)', `tt(w)', +`tt(-)', followed by a list of any of the characters `tt(r)', `tt(w)', `tt(x)', `tt(s)', and `tt(t)', or an octal digit. The first list of characters specify which access rights are to be checked. If a `tt(u)' is given, those for the owner of the file are used, if a `tt(g)' is @@ -2732,7 +2732,7 @@ of other users, and the `tt(a)' says to test all three groups. The `tt(=)', `tt(PLUS())', and `tt(-)' again says how the modes are to be checked and have the same meaning as described for the first form above. The second list of characters finally says which access rights -are to be expected: `tt(r)' for read access, `tt(w)' for write access, +are to be expected: `tt(r)' for read access, `tt(w)' for write access, `tt(x)' for the right to execute the file (or to search a directory), `tt(s)' for the setuid and setgid bits, and `tt(t)' for the sticky bit. @@ -2741,7 +2741,7 @@ Thus, `tt(*(f70?))' gives the files for which the owner has read, write, and execute permission, and for which other group members have no rights, independent of the permissions for other users. The pattern `tt(*(f-100))' gives all files for which the owner does not have -execute permission, and `tt(*(f:gu+w,o-rx:))' gives the files for which +execute permission, and `tt(*(f:gu+w,o-rx:))' gives the files for which the owner and the other members of the group have at least write permission, and for which other users don't have read or execute permission. @@ -2942,7 +2942,7 @@ item(tt([)var(beg)[tt(,)var(end)]tt(]))( specifies which of the matched filenames should be included in the returned list. The syntax is the same as for array subscripts. var(beg) and the optional var(end) may be mathematical -expressions. As in parameter subscripting they may be negative to make +expressions. As in parameter subscripting they may be negative to make them count from the last match backward. E.g.: `tt(*(-OL[1,3]))' gives a list of the names of the three largest files. ) -- 2.33.0