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 24445 invoked from network); 10 Apr 2021 20:57:26 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 10 Apr 2021 20:57:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20200801; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Content-Transfer-Encoding: Content-Type:Subject:Cc:To:From:Date:References:In-Reply-To:Message-Id: Mime-Version:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=8kk+PAVGPV/E/pwTY3ilgyYVnhdOiirUOR/Y+yUvxpU=; b=Tsos2cA0GltfATrf3Q/VKrSn1w yfpBZ31tuts1m6mB6sC4LjCe3pTuHF9YW8/VHnSGfxZEVSyTwHIsR1Ag5CK2wB2du8MRrSqAh+gf+ HDXOBW/xU/E5rCycv3oSIj+L/d+jHWTs0lPMrGJImMlyxa0yQLZZgHTfrDjlM2moZbbOZk9A89xCY 9EVEG6H9M+jQzcYugJZxdcXUkZrkaJU65HVc2Z3iWi7jF2PN3Z6z/fbHwaX9Ly4+Bs+B+1OZLs2id 3bs3bFIu+YvMnjR1CotzcRygNsCbeHs6/Q8uqsmso728xo9Kjin9Np05vJM9Y7CjwgdMvT5btu5Bm LXR5rbZg==; Received: from authenticated user by zero.zsh.org with local id 1lVKfV-000BvR-N2; Sat, 10 Apr 2021 20:57:25 +0000 Received: from authenticated user by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1lVKej-000BEh-Mc; Sat, 10 Apr 2021 20:56:37 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailauth.nyi.internal (Postfix) with ESMTP id 7A15627C0054; Sat, 10 Apr 2021 16:56:36 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Sat, 10 Apr 2021 16:56:36 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudekfedgudehjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepnfgr fihrvghntggvpgggvghljoiiqhhuvgiiuceolhgrrhhrhihvseiishhhrdhorhhgqeenuc ggtffrrghtthgvrhhnpeeufeehleeikeeijedtgffgteehheeivddtiedukeejvdejgfej udefkeevlefggeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehlrghrrhihvhdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidquddu hedukeejjedtgedqudduledvjeefkeehqdhlrghrrhihvheppeiishhhrdhorhhgsehfrg hsthhmrghilhdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1B004A00079; Sat, 10 Apr 2021 16:56:36 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249 Mime-Version: 1.0 Message-Id: <50a5ab7b-83b7-4602-8a3e-32139c59bb32@www.fastmail.com> In-Reply-To: References: Date: Sat, 10 Apr 2021 16:56:15 -0400 From: =?UTF-8?Q?Lawrence_Vel=C3=A1zquez?= To: zsh-workers@zsh.org Cc: "Bart Schaefer" , "Devin Hussey" Subject: Re: NO_CASE_GLOB and unreadable directories (Episode VI: A New Hope) Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Seq: 48482 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: On Sat, Mar 27, 2021, at 1:31 PM, Lawrence Vel=C3=A1zquez wrote: > On Sun, Jan 24, 2021, at 7:52 PM, Bart Schaefer wrote: > > I see these possibilities: > > 1) Do nothing; Devin's case is broken by design and termux needs to > > come up with a solution that doesn't involve NO_CASE_GLOB. > > 2) Adopt (a CYGWIN-clean variant of) my patch from workers/47832, an= d > > accept that some current usage of NO_CASE_GLOB will break. > > 3) Add a setopt (CASE_DIRS ?) for the current behavior, and merge th= at > > with workers/47832. I haven't yet worked out how to avoid having > > "setopt nocasedirs" imply the effects of "setopt nocaseglob" ... > > perhaps name it CASE_SEARCH (?) and simply leave the implication? >=20 > Is it safe to say we're going with 1) by default? bump (in the night) (actually late afternoon here) vq