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#65344: 28.2; Unable to Edebug cl-flet form which uses argument destructuring Date: Sun, 27 Aug 2023 08:34:23 +0200 Message-ID: References: <5184DD53-F121-405D-AEE9-6E72E17127EA@gmail.com> <87lee1nsvn.fsf@web.de> <875y53kaz7.fsf@web.de> <87bkevf1p7.fsf@web.de> <87edjpf804.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4932"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: brandon.irizarry@gmail.com, Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= , Michael Albinus , 65344@debbugs.gnu.org To: Michael Heerdegen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Aug 27 08:35:08 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 1qa9Ma-00015c-0P for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 27 Aug 2023 08:35:08 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qa9MS-00005P-LN; Sun, 27 Aug 2023 02:35:00 -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 1qa9MO-0008W6-EE for bug-gnu-emacs@gnu.org; Sun, 27 Aug 2023 02:34:56 -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 1qa9MO-00067k-5m for bug-gnu-emacs@gnu.org; Sun, 27 Aug 2023 02:34:56 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qa9MT-0006Lm-OE for bug-gnu-emacs@gnu.org; Sun, 27 Aug 2023 02:35: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: Sun, 27 Aug 2023 06:35:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65344 X-GNU-PR-Package: emacs Original-Received: via spool by 65344-submit@debbugs.gnu.org id=B65344.169311807724372 (code B ref 65344); Sun, 27 Aug 2023 06:35:01 +0000 Original-Received: (at 65344) by debbugs.gnu.org; 27 Aug 2023 06:34:37 +0000 Original-Received: from localhost ([127.0.0.1]:43915 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qa9M5-0006L2-AA for submit@debbugs.gnu.org; Sun, 27 Aug 2023 02:34:37 -0400 Original-Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]:42423) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qa9M4-0006Ko-Fu for 65344@debbugs.gnu.org; Sun, 27 Aug 2023 02:34:36 -0400 Original-Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-5298e43bb67so4654598a12.1 for <65344@debbugs.gnu.org>; Sat, 26 Aug 2023 23:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693118065; x=1693722865; h=content-transfer-encoding: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=msdSq/BMg37foim0bhANcjxM9u0Xj0cleVo5KYZVCnY=; b=a9v9JyXtyPkqJWpGKvs7FT/WjlU/RAfsI+zIPWtjq0grm81zUhf6cMw81tY5/W08H+ gIh+jhoBBsfHJlWgEd1+RUUtYDe2znMrW4bKXaTgWesgNPjh8/8woHgxmeief23bsE+s 57+h7MliKWDAYKcf3/eNRFZjqnNpU6qOgjP6Rbz24NQYtnB/dqtx4Ceu5mSVHCuhWoXm YDy3BV8qgZGcyZLV6R7u7TgDsECW5JNSFDp+4JcV5D5aEJTYmCcms2ORo9kZAE45/q0A 2xHk/hoinN2t2DueeKU72kBdG9wmHJaWZ08BoLUv75ikO/p/xPPSOW6KhEA/TBf34PkU t5RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693118065; x=1693722865; h=content-transfer-encoding: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=msdSq/BMg37foim0bhANcjxM9u0Xj0cleVo5KYZVCnY=; b=CWOfKoM9WuU3fSYVOwVwskMPCMrk0tD1zT5ghearpVHHq1OlXt4vC4FQ1aHDv44GB3 pbLgnzrq5hGF8BdKm713EFjsUbOunR6+1b4N1lr1z7xt8g4GvwQkGfciJhYBEkSlLYZO Sy2tSNUpIGBRkfhjGQeadSyeLENcELCCThCqcpkg0wOvlprqivJAi4rBaaHDcKKxs4vN tRahXpzkHRi9fhFPfi3GLt7jX7+MvAShAuZZFZ52h3fbM74AXwz3fhB1h9OMqEx6s+dm I6BmBP30ABocM1juERqBmKhCv/m6BVLEIrSnoA9RqeJaDkVp5KqBR87mQIljGBrufl5Q MioA== X-Gm-Message-State: AOJu0YyhJpnYHQ0tvXzOwGndhG+YwjDcVudJUuVLqEIP9ETpDuZmafS9 QbaHjDy3espDpIwBjbL7fCggaEFNtSfSG55j X-Google-Smtp-Source: AGHT+IFzIDnrmS0BfdV/TSrx28J5AsvziF5du/aCKv/grdJ3Y2io/YIz7wnr6GwFLFMQ74lt1NxDwg== X-Received: by 2002:aa7:de12:0:b0:522:3149:159b with SMTP id h18-20020aa7de12000000b005223149159bmr26450524edv.2.1693118064588; Sat, 26 Aug 2023 23:34:24 -0700 (PDT) Original-Received: from Mini.fritz.box (p4fe3a918.dip0.t-ipconnect.de. [79.227.169.24]) by smtp.gmail.com with ESMTPSA id d8-20020a05640208c800b0052237dfa82fsm2975280edz.64.2023.08.26.23.34.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 26 Aug 2023 23:34:24 -0700 (PDT) In-Reply-To: <87edjpf804.fsf@web.de> (Michael Heerdegen's message of "Sun, 27 Aug 2023 06:02:03 +0200") 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:268536 Archived-At: Michael Heerdegen writes: > Gerd M=C3=B6llmann writes: > >> Maybe you could give it a spin? I don't think I will. > > I did now. I can take control using &interpose using [] as its spec so > that nothing is consumed when the specified function is called. But > then it gets very complicated. > > This approach would only work if we catch the 'no-match tag thrown by > `edebug-no-match', and also catch the 'invalid-read-syntax' signal, > (there are several different types of failure involved, this makes it > much more troublesome). > > This can all be done, but it breaks the control flow of the Edebug > parser. The Edebug 'cursor' (current parsing position AFAIU - there can > be multiple cursors in use) is implicit, so I don't know and can't > control where to continue in the 'no-match case. I gave up at this > point because it was obvious that we will not want to do this. Ok. Thanks for trying it out.=20