From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#65516: 30.0.50; Edebug behavior of signaling errors in &or Date: Mon, 28 Aug 2023 07:52:13 +0200 Message-ID: References: <878r9w8548.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14922"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Michael Heerdegen , 65516@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Aug 28 07:53:13 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qaVBZ-0003cR-6M for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 28 Aug 2023 07:53:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qaVBO-0005tS-Qq; Mon, 28 Aug 2023 01:53:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qaVBN-0005tJ-JF for bug-gnu-emacs@gnu.org; Mon, 28 Aug 2023 01:53:01 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qaVBH-00030k-PO for bug-gnu-emacs@gnu.org; Mon, 28 Aug 2023 01:53:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qaVBN-0007NS-Td for bug-gnu-emacs@gnu.org; Mon, 28 Aug 2023 01:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 28 Aug 2023 05:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65516 X-GNU-PR-Package: emacs Original-Received: via spool by 65516-submit@debbugs.gnu.org id=B65516.169320194928318 (code B ref 65516); Mon, 28 Aug 2023 05:53:01 +0000 Original-Received: (at 65516) by debbugs.gnu.org; 28 Aug 2023 05:52:29 +0000 Original-Received: from localhost ([127.0.0.1]:46735 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qaVAr-0007Mf-Ez for submit@debbugs.gnu.org; Mon, 28 Aug 2023 01:52:29 -0400 Original-Received: from mail-lj1-x231.google.com ([2a00:1450:4864:20::231]:50359) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qaVAp-0007MT-Hm for 65516@debbugs.gnu.org; Mon, 28 Aug 2023 01:52:28 -0400 Original-Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2bcc14ea414so42568091fa.0 for <65516@debbugs.gnu.org>; Sun, 27 Aug 2023 22:52:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693201935; x=1693806735; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=YqWHad/XeZfl73DaUOIKh+MSM/CNXqchTNsej1coJoc=; b=hPwkFCPiE3JqEhv/miFyQ6eBDDGdr2+yAcZ094VIKvnjkmsagFLvE74LmiBdZqB6bJ VXC3AcJSK2+923b9rn43e/uIfiRLzOlr4O0PG2vHHIpS+fMb9IrNisn/JBppzcyG5xZo aPbbTu1vyFbiiNfwFpMSdsaIaI4ZnFhdvuGVieJ0AQPoeATWkV28YSAtL6u07YLekXDH V2fZif4oHXYjMjjTxCmehJaZ2xnR8QXO4LsA9FjOH1lNF4V47aow3M5e85F4ewtc2EuN GVz2mMe4c8i53T72rpINKJUkOwqQFkQ2DHKTieH/lmfs/YivLZWiw0C816Vi6SAIQCOy NC6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693201935; x=1693806735; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=YqWHad/XeZfl73DaUOIKh+MSM/CNXqchTNsej1coJoc=; b=bhrEMiqNKsHQ8Aqgzbb7zJDYHrgKAvngw0Xmx8CwSZhT/RNo8BhjQqCmCZ1IxmCqjG ijlFSDBW5Au9mYJQGEOsJCKtx0cCd0LqOlucRH9dALXZJA7Alx9/NApOflj2wtsw4R8L WzHW/kYDgh4bDpRCWgG9hIcn0Kk1C2S6At13adq31cgd4G6Rzii2lOKKOP6JBx+jj0Go y9bkuqbT9m70zUAoVRgnONnUxxpeUKvU1YwKpONKXcFXy0Ym2ujxJIyE0jMZFbApDr7B 5z/e4QHzP5K4pcNnvgnljDjB7hiO1onUvbOoq2Xj3/P5FZQAE+NuRGhsnjiZhA/PaR/x 3r9A== X-Gm-Message-State: AOJu0YyzK4UfDdSicjnCwwbTkOl6AtQYOiF5NwkJ9xLPnHf1NSGhgm4g mWIdYnidEH+OlODys4yAe4eiGPN2FJQ3fDYS X-Google-Smtp-Source: AGHT+IFnxcLrJds5Ck2cnR4yKclibiE3fUiTf1GsH88pxU19WVXc2q03dRrQvoCRqdOsW4V1GGdEzw== X-Received: by 2002:a2e:b786:0:b0:2bb:a123:2db7 with SMTP id n6-20020a2eb786000000b002bba1232db7mr17546448ljo.51.1693201934703; Sun, 27 Aug 2023 22:52:14 -0700 (PDT) Original-Received: from Mini.fritz.box (pd9e36867.dip0.t-ipconnect.de. [217.227.104.103]) by smtp.gmail.com with ESMTPSA id gy25-20020a170906f25900b00985ed2f1584sm4243086ejb.187.2023.08.27.22.52.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 27 Aug 2023 22:52:14 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Sun, 27 Aug 2023 23:26:34 -0400") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:268604 Archived-At: Stefan Monnier writes: > Michael Heerdegen [2023-08-28 00:58:31] wrote: >> Stefan Monnier writes: >>> Hmm... actually, looking at `def-form` again it seems it doesn't use >>> `&define` nor `(edebug-)gate`. >> Dunno if this helps, I'm understanding it only half, but AFAIU, >> `def-form` falls back to `edebug-form' which looks at &define and uses >> `edebug-gate' indirectly when calling `edebug-list-form'. > > Hmm... Could be, indeed. In any case, this "gate" business is > quite messy. Yup :-) > > I'd be tempted to start removing uses of it, bit by bit, to try and see > what breaks. And if needed, maybe add a new replacement for it that > would be better defined (I'm imagining a kind of "scoped gate", which > could look like `[&gate-in ... [&gate-lock ...SPECS...] ...]` such > that if `...SPECS...` fails to match, we propagate this failure > immediately up to the `gate-in`). > > This way > > [&gate-in [&or ["foo" &gate-lock ...] > ["foo" "bar"]]] > > would never fallback to ["foo" "bar"] whereas > > [&or [&gate-in ["foo" &gate-lock ...]] > ["foo" "bar"]]] > > would fallback to ["foo" "bar"] if "..." fails to match. That's a possibility. I can't say much more because I fail to understand the motivation why gate is used in the first place. What did the developers using it want to achieve?