From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28969 invoked by alias); 12 Feb 2018 16:34:40 -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: List-Unsubscribe: X-Seq: 42360 Received: (qmail 26205 invoked by uid 1010); 12 Feb 2018 16:34:40 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf0-f53.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.215.53):SA:0(-1.9/5.0):. Processed in 2.716594 secs); 12 Feb 2018 16:34:40 -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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: simon.a.let@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=OitZE1lFjywlsZeoFeKVO6bJHYXDW0nrxO+uDFNwOBI=; b=ttdmSkrLDsKzJhasQUFgCCv2haztXJHTn/xTxMOudLoMJDoQlWcLIfh+T9v7jPD6IG HUz9baLddo17vzFNygW/RakglZj7NmaeJULuGy2Exb19fRBOsAII5WxRAIQA5EeA+RML IXNM+TMlGeKyVIojLm8GdoW38n1jQAqlpLhiG+/yFZv0XzNsx/5jfD6vmXMjbTABQAB/ Gd3bDqN+7EJzWn+BA2atihP6YaZyjXPWzj3K8QDPfCwu6i1RS69oS+Z/Umkx1durcpjx BF5XAEt0G2TcEkXzC+EXwmGlJfTnbKyx2RW5l5fRGcx0i7KCUDDqyHJmYNTtawKTcSAy e1EQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OitZE1lFjywlsZeoFeKVO6bJHYXDW0nrxO+uDFNwOBI=; b=Y/bO0u0+m3TJMPR+GVSz9HVAqKhOysvC4WhV8a280qsQUg6XU+S9wGuq+slFuREqV8 D+bakFXh3rRdriNb+OjnYk1SLLloD7BP/Ef0wGb9NAJlZL0KgH+QnwNwq9oPKoBICE8t otQxhEeRvipW3oCgQN5XlRw7anP1Awz/eUEgNQG3xerv3jo5pjFN3HlzZHziy7OaldoF JuUA0yl7oqYzWS3UhqkmK0o5r19AAnCXdkCw2XUk6P4aItWqEwMF25wBCzyVeyUoL8m7 ErURSVyyA08MRq8kForEGDCgHq/BBdyA3lmNGJc6F8jD7VqVdPBX8Zg7z2LcIBzVQ2Ud bxRQ== X-Gm-Message-State: APf1xPA17C7rdkGHTCU4H1uMIY27W+SOPWN5xkiG+KDMV+38qUdUAr8u 6oKAAKBaD30iF4UhTu/0hQPqDWxWHmrumANaw54= X-Google-Smtp-Source: AH8x225M+w2g18U1d3PI7luc4GH6RQ0RaNB4/TbJ3PeZxQwNQMM0BoXrNF0TAF5xVjQ3L4cqHkAZP+0qSvc6CQODUqA= X-Received: by 10.46.108.9 with SMTP id h9mr7433462ljc.125.1518453272043; Mon, 12 Feb 2018 08:34:32 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?Q?=C5=A0imon_Let?= Date: Mon, 12 Feb 2018 17:34:11 +0100 Message-ID: Subject: Issue: Handling of globbing fails To: zsh-workers@zsh.org Content-Type: multipart/alternative; boundary="f4f5e8079118e366ce05650673c2" --f4f5e8079118e366ce05650673c2 Content-Type: text/plain; charset="UTF-8" Hi, I want to create an issue. The way zsh handles globbing fails is non-systematic. Consider running following command: `echo some_empty_directory/* && echo "NO FAIL" || echo "FAIL"` It produces following output: `zsh: no matches found: some_empty_dir/*` The command causes globbing fail but the way zsh handles this fail is beyond me. Why does globbing fail stop execution of the current line (or script)? This behavior is non-systematic or surprising at least. Why does failed globbing behave almost as a parsing error? Cheers, Simon Let --f4f5e8079118e366ce05650673c2--