From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 1d1dc786 for ; Tue, 20 Aug 2019 11:05:46 +0000 (UTC) Received: (qmail 20292 invoked by alias); 20 Aug 2019 11:05:36 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24165 Received: (qmail 9876 invoked by uid 1010); 20 Aug 2019 11:05:36 -0000 X-Qmail-Scanner-Diagnostics: from mail-wr1-f54.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25545. spamassassin: 3.4.2. Clear:RC:0(209.85.221.54):SA:0(-2.0/5.0):. Processed in 1.583648 secs); 20 Aug 2019 11:05:36 -0000 X-Envelope-From: stephane.chazelas@gmail.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.221.54 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=bR9cQL28MtQkploYuI6r5AorQ89DiohrWDqfvdl/K0I=; b=G3DCSoQ7tRFh3mMByz5ktv0A9sntIqC8npmFiTIRBGZ2j4Qa9nN1rZ2Wh6T65JjFYS 6mWNV8swVrCyRoC2uWm39MRCY3IDXM/Ey1NMXKTiPrHJ1HirN68Sv+frD2UBHVWmYcID h3ONyA4PV5Ie5AMAMW2lsnP3XVUUzyV8lfZYGUlZIxCvghlH5aUtwZvwnEZ0aGjLO6vY X7q96d/3AWzdUpCzr+P8NNwjx75KEoZ7nclkx8HSaT+iT5gFiCGyGR5+0cvJQneYBqt3 dfPzfcDk7dHk2EEcLblw5Wtyj6vBYL9zbhkRmlNZ1WD0N67UtB2ZJzBQw/G5yzO+u6R0 o/Kg== 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:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=bR9cQL28MtQkploYuI6r5AorQ89DiohrWDqfvdl/K0I=; b=Py6sWrmShYaH1LQUCWNAxHuIP2pPuBFsAU5jERP+2Z7VsisdGEZHN71wtiROSwlxe1 +jE3oVgN/O0eWHF8+QW/tT7Kyqub3Yl/MBmBdL9vMJBnXZAunR1Mk7BJZ/dSC/wLUiO7 0lT+TpvJdoivH9gMTilBhPWbUQ+Yk2hxbsTtm4HI3zPVEt70GcVWnPsqdBBq+kt4b8oE iS/ZujZq2tbuJn9qtwoMeTx0mD8uDdEhPgN+3NFA+kMGN9Wo4zTdw5zgZnyddTYxLM+T 7fDp8UJOI4xKePL2qfa2YLFcl6N25bZuwJn7n6KbGZeC8CKuSBiSbsXt1lFYYHjUk0iR HpbA== X-Gm-Message-State: APjAAAWjOMjsXGS0Y7Ql7ICx7G2Jf6Ge8zZIe86+YaZzE0vV1a0PlVWy 6Sv+4Ik6B4LBW6wVwUp8fOYPrMX8ehU= X-Google-Smtp-Source: APXvYqzm1qCHjmpplvxrtmIzCdt3T6RET37GDDhhyPXqEzO3YLrO8P2EuAHrFp+jo48oFl9d3xig0A== X-Received: by 2002:a5d:480e:: with SMTP id l14mr32800662wrq.96.1566299100912; Tue, 20 Aug 2019 04:05:00 -0700 (PDT) Date: Tue, 20 Aug 2019 12:04:58 +0100 From: Stephane Chazelas To: Aryn Starr Cc: Zsh Users List Subject: Re: Help wanted with debugging a weird glob behavior Message-ID: <20190820110458.slvco7oybg27i7hf@chaz.gmail.com> Mail-Followup-To: Aryn Starr , Zsh Users List References: <0628A0E5-63F0-481E-AEC2-962658134620__9154.55124793283$1566242642$gmane$org@icloud.com> <20190820073701.wcrxekoejx7xi77x@chaz.gmail.com> <227BE55C-4B7E-4CAD-B212-D48F663BC09D@icloud.com> <20190820082150.usmq3gmh3wdipg3g@chaz.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20171215 2019-08-20 13:32:31 +0430, Aryn Starr: > Indeed, I do have `nocaseglob` :) Can’t zsh be made to try to > match the decomposed form, too? (Perhaps as a new option?) I > don’t think putting `iconv`s everywhere is a sustainable > practice … [...] I suppose we could have an option similar to nocaseglob like unicodeequivalenceglob where U+00E9 would match both U+00E9 and U+0065U+0301 and vice-versa for instance (which you could combine with nocaseglob and could probably be abused in a number of ways and cause all sorts of security vulnerabilities like that HFS+ design and case insenstive FS/nocaseglob already do). I don't know if there's a standard C API for that. zsh may need to pull an ICU library dependency to implement it. Also note that normalisation changes with each version of Unicode (like case insensitive comparison already changes with the locale and version of the locale/system). That sounds overkill just to work around the misdesigns of macOS. -- Stephane