From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15433 invoked by alias); 3 Jun 2018 18:48:33 -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: 42924 Received: (qmail 13224 invoked by uid 1010); 3 Jun 2018 18:48:33 -0000 X-Qmail-Scanner-Diagnostics: from mail-wr0-f193.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.128.193):SA:0(-2.7/5.0):. Processed in 1.136177 secs); 03 Jun 2018 18:48:33 -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.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: tamelingdaniel@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=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=Qt+rqMmIvMbhNpERg2t3x11DxPAJKhJVriogseMAcQs=; b=WnQ9Ut8+ZxKN5Hj5DTDFGwVDlS7mAfYIJFTaIHwOLm/IFEpvRJOPpXj+YoDx4Hg/Jg r1kBIHCUQh6BmgNoM5+v9rMQhh670qOkrxIYAMlh2ueGmpjjDUerPiVAdWMK9vsl5YJT PS9WHgkHNtEit+jlDBCaWCdDkxkeZO9L7Ur3Tjb/u5GQ5Id8+JFSqQwLFNaLrujP6Kr9 AgizFEQhGfyu8Wz53lRJk8G2Ij7+KIYGLxyFoGsDTERO5MtPIIExYSmPWB0lfCxOiILI Z6dy41CxO61Txg3iCbPepmhYMPylfWiobKFILChMpOOwYo3oV0IhXHT+7Ct9nKPZMZK2 zxVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to; bh=Qt+rqMmIvMbhNpERg2t3x11DxPAJKhJVriogseMAcQs=; b=jqW5bcz+VEo8DXjOBFr8wISToFDW/U+ouv07D2e5TlFL3OIWFFhWUFuYlF7YefivK0 Jhaa1ikoEHf7ujvLx7gwzr1LNA43/6ehhxo2Q3zbyVKMRb5B8iF8HW4Z4gbmLU0Y7erR cDnb9TFfDONInu/8v/eQ7czO84p8HhOM535wf14IBJY7mWMHauWnLqK5TZcVokbt836P 28cZl7cUIn7xK05kTg6xsHN1vcylaVJsMAhifLbNyWcHlUZzD9cEmWQ2l4axwkrVm1mL MTwlXhp7pd+7aQpKo9UxIw46CsoIHyIrtQILsBxqkdWWPVnjwVFidQYil6jMuVdswD6O Gs+Q== X-Gm-Message-State: ALKqPweyWN77ND+5o/U/FsqaNRMUQoxIpEioDmnfYnfJ+lWIRBi7lWpT 3vzIik1dcB9lEMmygPC52UTWCg== X-Google-Smtp-Source: ADUXVKICela9Xx/ywKswFpqdx0/d4gfnAEuNktkrxpC+LjM9TzOr1xnnNbgaOugMD9ZnbsgK+ytXXw== X-Received: by 2002:adf:8290:: with SMTP id 16-v6mr13770580wrc.38.1528051707910; Sun, 03 Jun 2018 11:48:27 -0700 (PDT) Date: Sun, 3 Jun 2018 20:48:26 +0200 From: Daniel Tameling To: zsh-workers@zsh.org Subject: Re: [Bug] Strange Globing Behaviour when used with sudo Message-ID: <20180603184826.xmmjp7woexdivyl7@Daniels-MacBook-Air.local> Mail-Followup-To: zsh-workers@zsh.org References: <20180531094403.05b62bee@camnpupstephen.cam.scsc.local> <20180531084938eucas1p19a854d9e9ea17428cd6549f56a283356~zroN76sl33019130191eucas1p1K@eucas1p1.samsung.com> <3977A049-90E6-4EDD-9E4C-8D2FF38593A3@kba.biglobe.ne.jp> <20180531152941eucas1p2c45927fa47f727224e2da98b4f6a7604~zxFgS-BM50307003070eucas1p2G@eucas1p2.samsung.com> <20180531181546.osffv3ysjzaxjfid@Daniels-MacBook-Air.local> <01B9BB58-DDAE-4056-AD9A-2367DC3AC20D@kba.biglobe.ne.jp> <20180602181719.vzcnij3fvx7eueuk@Daniels-MacBook-Air.local> <7D035B65-A2BA-49F3-807D-A387FF4FE6DB@kba.biglobe.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7D035B65-A2BA-49F3-807D-A387FF4FE6DB@kba.biglobe.ne.jp> On Mon, Jun 04, 2018 at 01:30:14AM +0900, Jun T. wrote: > > Do we need to fix (or workaround) this problem, given that > very basic commands like "ls" are also broken on macOS? Personally, I would say no. I find that the workarounds make the code very ugly. Then there is the resulting inconsistency with other commands. Moreover, as the weirdness occurs only with sudo, it is also very difficult to make sure that we fix all that could go wrong and don't introduce any unwanted side effects since globbing with sudo will be rarely used. So I wouldn't do anything, but would also be fine with something small that addressed the original problem, like your previous patch. > > Btw: > > I noticed bash manages to trigger the ls error message when zsh > > outputs "no matches found" > > $ bash -c 'ls */..' > > ls: cannot access '*/..': No such file or directory > > Try 'setopt no_nomatch'. See the option NOMATCH in zshoptions(1). Thanks. -- Best, Daniel