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 26797 invoked from network); 14 Oct 2021 20:25:34 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 14 Oct 2021 20:25:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20210803; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Message-ID:Date:Content-ID: Content-Type:MIME-Version:Subject:To:References:From:In-reply-to:cc:Reply-To: Content-Transfer-Encoding:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=LieuRJiJcGE69kPifB5EOJKSL2WzKDpzRhVmihZVJIk=; b=kywr8vpces3vQDA8NrMJdFJ3tZ 4kOX7f9aDLESz1Dc+jGydpP6tVX+v+1sktsKftvawg0Ua8S2obTkZTJLFddrgUjc7XLQbEBO4CpiX VylVZgmKwNod2clPcS8yk2pKUZfaKfrou4MjWuJnb8cO7wtAKYj+y4VkOP45Oo7X8YGlLjs9i4k9U 4Yr/K4sQ86A1LtsDJouQ9jFw9IHAs3QdXPHJ9MFCD5X8Dvg8W+SlrrJDzFLk+/r3l45UmsV2agcJa vQ7/x51DOh2nLvbfICBr0xGFDey/ALKKNxkLs4zvAIp61q8WJvTMH1/qoH/jdwowF8ZkHWbQwNyGB piwY5ghA==; Received: from authenticated user by zero.zsh.org with local id 1mb7IC-000CDS-5O; Thu, 14 Oct 2021 20:25:32 +0000 Received: from authenticated user by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1mb7Hs-000Bwk-OH; Thu, 14 Oct 2021 20:25:12 +0000 Received: from [192.168.178.21] (helo=hydra) by mail.kiddle.eu with esmtp(Exim 4.94.2) (envelope-from ) id 1mb7Hr-0005hd-SP; Thu, 14 Oct 2021 22:25:11 +0200 cc: Marlon Richert , Zsh hackers list In-reply-to: <20211013193740.GA27436@tarpaulin.shahaf.local2> From: Oliver Kiddle References: <20211012152532.GC17948@tarpaulin.shahaf.local2> <20211013193740.GA27436@tarpaulin.shahaf.local2> To: Daniel Shahaf Subject: Re: [RFC] Add xfail tests for || form of completion matchers MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21923.1634243111.1@hydra> Date: Thu, 14 Oct 2021 22:25:11 +0200 Message-ID: <21924-1634243111.877087@uSgx.0zsB.xvOO> X-Seq: 49487 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: Daniel Shahaf wrote: > That's not how it works. Documented semantics are API promises that > should be presumed to be used in the wild. Any change that may break > anybody's proverbial spacebar heating is an incompatible change and > should be treated accordingly (avoided if possible, and failing that, > clearly documented for upgraders, designed with a reasonable failure > mode for old code on new zsh, etc.). The existing documentation and implementation don't entirely match. Following the history of the feature including original list posts, I think it is fairly clear what the intended behaviour is supposed to be. The behaviour has inconsistencies, quirks and bugs and even determining what the behaviour is in a form that could be documented is not easy. Many of your questions do have answers buried in the long thread that started this. I'm happy to see better documentation and test cases will make it easier on anyone brave enough to attempt to fixup issues. I've not had a chance to review the patch properly but will do. Oliver