From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3617 invoked by alias); 4 Jun 2017 00:32:51 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 41210 Received: (qmail 5757 invoked from network); 4 Jun 2017 00:32:51 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f176.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.217.176):SA:0(-2.8/5.0):. Processed in 1.597399 secs); 04 Jun 2017 00:32:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.176 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=ZEWJF7OUFvr60MqmpzmOKa/JP4x4w2KkEWqTnG0MUL8=; b=eoEpZ79SWg32Ww2BDKvalEnGLxSyVoiBEpB69b1YY90lkWz7gumHbYDCYwtNQsXxGt OVatTBHn8xNe5OkNSJ2/k9H2GWHhFE1olNwBweRzKp+1K63W3AAxNGutcw4wEcPNZbhf YyiYIjqiBAMA0h7BY2RZKRo8CGLIEAmsGdzc/SwBK8mQhtAm5JDqgO11dVg0p61Jgjl+ G2F7lfJDywqnhYYTxuRg+1v3eTJeUqc2eZQ2jmD4jpcYYWQmko7yu00HszfJVmqBRonO 1VL5z/6ErJ8nXRkEqEkP5Z4cuTMUA9H3HvkQw6+GDt9Nkwty4yFl5QaHniUpIuPHeFBz pvqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=ZEWJF7OUFvr60MqmpzmOKa/JP4x4w2KkEWqTnG0MUL8=; b=pd5qtAgRg1W526+2g5Mi7RtZgz7wtQBKQycrCR/Jo1Q9rej1HhEJvuXvJGYdPfALBB 1BNdWaJvnQnuLQqQAJeNydExB/2OouLt5fnp8EsVLNe9uL3qCX7Y9VFKtgQ3UScxF3dx LBBOU57yMTjUhvyJW++cN5XkLB1dELe2Cf9vsOC8QHt3ixq2/7e2LoGMWT6h9T2QAusX aZjF7lIjuveH+LH2SSStHO4X03ZImMzeS3hQcCkaVO3dFMWlkCN54XVB0OM/aytT8hfN +FeEW74b0jQavx3MaaLPGQiOxAq0aiwJ/aJaqZd/7oMzhxER8PaEn6UfPhBB5GcH+3Cu Hoiw== X-Gm-Message-State: AODbwcBwo/A7wmaIj+vP7WfUZDY8D4wHCmQX8TjmFLHo3Rxkuw1x4db9 PLZSxBtZ8oWrpgxKLBo= X-Received: by 10.176.91.209 with SMTP id z17mr7853513uae.49.1496536364782; Sat, 03 Jun 2017 17:32:44 -0700 (PDT) From: Bart Schaefer Message-Id: <170603173306.ZM15972@torch.brasslantern.com> Date: Sat, 3 Jun 2017 17:33:06 -0700 In-Reply-To: Comments: In reply to Sebastian Gniazdowski "(Z) flag translates >! into >|, just mentioning" (Jun 3, 7:41pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: (Z) flag translates >! into >|, just mentioning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 3, 7:41pm, Sebastian Gniazdowski wrote: } } This is not harmful as >! and >| are equivalents, but I have to ask, } does someone know about other such replacements? It also converts >&! into &>| (and similarly for >>! >>&! too). This is because the lexer is invoked by (z) and canonicalizes those tokens. You'll note that the output of "set -x" is altered in the same way.