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 23425 invoked from network); 31 Mar 2021 09:25:52 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 31 Mar 2021 09:25:52 -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:Message-ID:Date: Content-Transfer-Encoding:Content-ID:Content-Type:MIME-Version:Subject:To: References:From:In-reply-to:cc:Reply-To:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=v7VWUAtgp6seNOKAsXJy4sq4EXczprPxeh9CrMHfF/8=; b=R2/wcD+UO2oA229CzfigvZYpz3 WYjnEIvRWcAoAEZOdctvmnG4IpFMj2jMduClTqrkfR4kqN3UVfXqx7QJwcebPfA2sMjcKnlYe077c oPr0yf/gXJo6mJJyUeJHfRj/UQsvBdV5wb7PJFJNf88zvG0TA5JGtIzjyNFENvqQRanKCwG+j9rtx xtuP19okbMnWUIhHrWbI9bi8hHb3doHVJ9qIZwIRtfz40nLfpclxApzhQQ+sCMwue6LqF2D7nTLkE 1MWrkuPpDDMBHT/ER0wwNnBtrB/tMBggXcA4Vs2YM0PlLvIUp/ppOPo17MBoEljAq2Bjpy+SXPrha Bfw9fR/Q==; Received: from authenticated user by zero.zsh.org with local id 1lRX6m-000Gos-J6; Wed, 31 Mar 2021 09:25:52 +0000 Received: from authenticated user by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1lRX6U-000GfD-Mj; Wed, 31 Mar 2021 09:25:34 +0000 Received: from [192.168.178.21] (helo=hydra) by mail.kiddle.eu with esmtp(Exim 4.93.0.4) (envelope-from ) id 1lRX6T-000Dju-5Z; Wed, 31 Mar 2021 11:25:33 +0200 cc: Zsh hackers list In-reply-to: From: Oliver Kiddle References: <74277-1616967738.353098@Tsys.Nn18.rMz7> To: Marlon Richert Subject: Re: Why does _main_complete not try the next completer when $_comp_mesg is non-zero? MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <52816.1617182733.1@hydra> Content-Transfer-Encoding: 8bit Date: Wed, 31 Mar 2021 11:25:33 +0200 Message-ID: <52817-1617182733.169625@8lsJ.YVQX.sx5d> X-Seq: 48349 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: Archived-At: Marlon Richert wrote: > I've been using some variation of the code below in my > [zsh-autocomplete plugin] > (https://github.com/marlonrichert/zsh-autocomplete) since last July > (so, for about 9 months now) and I have yet to experience any issues > from it, nor have any of my end users reported any issues from it. > That’s why I’m asking whether the behavior upstream is actually > necessary. Perhaps I wasn't clear in my reply but yes I do regard it as necessary. Maybe that code doesn't cause "issues" but it does change behaviour and stop completion from working in the way I've come to expect it. There are some related aspects of the current behaviour I'm not especially keen on like _guard not taking a tag and situations where you get both the description and the message constructed from the format style with the warnings tag. Those should be two distinct cases and to cover your use-case there might be a way to control whether completion continues. What does your completer style look like out-of-interest? Do you set zstyle ':completion:*:warnings' format ? Oliver