From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.bugs Subject: bug#66149: Mistyping a search breaks keyboard macro Date: Sat, 23 Sep 2023 11:43:56 +0300 Message-ID: <1fefaf0472e92c20b0170b02c0ad3820b10e8978.camel@yandex.ru> References: <2bba5a744feb000a4ffc1fef79d223fcf24953e7.camel@yandex.ru> <83sf7678fv.fsf@gnu.org> <86fs36ql6i.fsf@mail.linkov.net> <61c24e6086f4ce5125d78490a587c1d1193f65dc.camel@yandex.ru> <834jjl5nfr.fsf@gnu.org> <4fccb4b82092c7fa085527597561d0f66e12eb9b.camel@yandex.ru> <8334z55ls0.fsf@gnu.org> 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="25848"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.48.4 Cc: 66149@debbugs.gnu.org, juri@linkov.net To: Eli Zaretskii , Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Sep 23 10:45:05 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 1qjyG8-0006Va-Tk for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Sep 2023 10:45:04 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjyFx-0001hO-1C; Sat, 23 Sep 2023 04:44:53 -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 1qjyFv-0001gx-8f for bug-gnu-emacs@gnu.org; Sat, 23 Sep 2023 04:44:51 -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 1qjyFu-0007Fv-MQ for bug-gnu-emacs@gnu.org; Sat, 23 Sep 2023 04:44:50 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qjyG5-0006ci-N5 for bug-gnu-emacs@gnu.org; Sat, 23 Sep 2023 04:45:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Konstantin Kharlamov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 23 Sep 2023 08:45:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66149 X-GNU-PR-Package: emacs Original-Received: via spool by 66149-submit@debbugs.gnu.org id=B66149.169545865425375 (code B ref 66149); Sat, 23 Sep 2023 08:45:01 +0000 Original-Received: (at 66149) by debbugs.gnu.org; 23 Sep 2023 08:44:14 +0000 Original-Received: from localhost ([127.0.0.1]:37749 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qjyFK-0006bD-7R for submit@debbugs.gnu.org; Sat, 23 Sep 2023 04:44:14 -0400 Original-Received: from forward500a.mail.yandex.net ([178.154.239.80]:42892) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qjyFG-0006b3-Qq for 66149@debbugs.gnu.org; Sat, 23 Sep 2023 04:44:13 -0400 Original-Received: from mail-nwsmtp-smtp-production-main-39.vla.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-39.vla.yp-c.yandex.net [IPv6:2a02:6b8:c0d:31b:0:640:fdf8:0]) by forward500a.mail.yandex.net (Yandex) with ESMTP id D14915E6FD; Sat, 23 Sep 2023 11:43:57 +0300 (MSK) Original-Received: by mail-nwsmtp-smtp-production-main-39.vla.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id uhHdV6FsJOs0-XIZJiMXG; Sat, 23 Sep 2023 11:43:57 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1695458637; bh=n1bc9DB9NNibECOWGNSMM7bQXA+TGuGvZ33o6dr7nIg=; h=References:Date:In-Reply-To:Cc:To:From:Subject:Message-ID; b=OrkX4+MvfarfcFEYRzovdXfSThzJFTAv9D0h0q3rz4mpdWMR39nK0btI6oOU64Kjy Gxmc63H1lujdoMVIUatOx9JCKuJXAOycjcCou1mAAItrj8vaVrSqmVJWpp+jT6GJsu P38DonlI6xJc9AYa2SrfE0L0f+/c2+DFUnM7bsr0= Authentication-Results: mail-nwsmtp-smtp-production-main-39.vla.yp-c.yandex.net; dkim=pass header.i=@yandex.ru In-Reply-To: <8334z55ls0.fsf@gnu.org> 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:271146 Archived-At: On Sat, 2023-09-23 at 11:36 +0300, Eli Zaretskii wrote: > > From: Konstantin Kharlamov > > Cc: juri@linkov.net, 66149-done@debbugs.gnu.org > > Date: Sat, 23 Sep 2023 11:01:32 +0300 > >=20 > > On Sat, 2023-09-23 at 11:00 +0300, Eli Zaretskii wrote: > > > > From: Konstantin Kharlamov > > > > Cc: 66149@debbugs.gnu.org > > > > Date: Sat, 23 Sep 2023 10:14:59 +0300 > > > >=20 > > > > On Fri, 2023-09-22 at 18:41 +0300, Juri Linkov wrote: > > > > > >=20 > > > > > I have no opinion whether 'ding' should terminate kbd macro > > > > > or > > > > > not. > > > > > But it's possible to customize 'isearch-wrap-pause' to 'no- > > > > > ding' > > > > > to not ding on isearch failure, then kbd macro is not > > > > > terminated. > > > >=20 > > > > Oh, thank you! So for example, having the following code in the > > > > init > > > > file works around the problem: > > > >=20 > > > > =C2=A0=C2=A0=C2=A0 (defadvice kmacro-call-macro (around align-regex= p-with- > > > > spaces > > > > activate) > > > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (let ((isearch-wrap-pause 'no-ding)) > > > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ad-do-it)) > > > >=20 > > > > I'll post an answer about that on the emacs.stackexchange then. > > >=20 > > > And I'm closing the bug. > > =C2=A0 > > Why? The problem is still relevant. A workaround is not a fix. >=20 > because the motivation to make any such changes is now even lower > than > it was before, and I don't want to keep bugs open when nothing is > being done for them, nor ever will be. Oh, okay, so, a fix for this closed bug will still be accepted? I was thinking of making a fix at some point in the future. Not right now I as I don't have resources ATM, but the problem overall seems to be easy to fix.