unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <Hi-Angel@yandex.ru>,
	Stefan Kangas <stefankangas@gmail.com>
Cc: 66149@debbugs.gnu.org, juri@linkov.net
Subject: bug#66149: Mistyping a search breaks keyboard macro
Date: Sat, 23 Sep 2023 11:36:15 +0300	[thread overview]
Message-ID: <8334z55ls0.fsf@gnu.org> (raw)
In-Reply-To: <4fccb4b82092c7fa085527597561d0f66e12eb9b.camel@yandex.ru> (message from Konstantin Kharlamov on Sat, 23 Sep 2023 11:01:32 +0300)

> From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> Cc: juri@linkov.net, 66149-done@debbugs.gnu.org
> Date: Sat, 23 Sep 2023 11:01:32 +0300
> 
> On Sat, 2023-09-23 at 11:00 +0300, Eli Zaretskii wrote:
> > > From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> > > Cc: 66149@debbugs.gnu.org
> > > Date: Sat, 23 Sep 2023 10:14:59 +0300
> > > 
> > > On Fri, 2023-09-22 at 18:41 +0300, Juri Linkov wrote:
> > > > > 
> > > > 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.
> > > 
> > > Oh, thank you! So for example, having the following code in the
> > > init
> > > file works around the problem:
> > > 
> > >     (defadvice kmacro-call-macro (around align-regexp-with-spaces
> > > activate)
> > >       (let ((isearch-wrap-pause 'no-ding))
> > >         ad-do-it))
> > > 
> > > I'll post an answer about that on the emacs.stackexchange then.
> > 
> > And I'm closing the bug.
>  
> Why? The problem is still relevant. A workaround is not a fix.

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.

I'm okay with reopening for some limited time, but we should then say
in advance when it will be closed if no progress is made.

But maybe Stefan (CC'ed) thinks differently?





  reply	other threads:[~2023-09-23  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  8:09 bug#66149: Mistyping a search breaks keyboard macro Konstantin Kharlamov
2023-09-22 11:29 ` Eli Zaretskii
2023-09-22 11:40   ` Konstantin Kharlamov
2023-09-22 15:41   ` Juri Linkov
2023-09-23  7:14     ` Konstantin Kharlamov
2023-09-23  8:00       ` Eli Zaretskii
2023-09-23  8:01         ` Konstantin Kharlamov
2023-09-23  8:36           ` Eli Zaretskii [this message]
2023-09-23  8:43             ` Konstantin Kharlamov
2023-09-23  8:58               ` Eli Zaretskii
2023-09-23 12:56             ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8334z55ls0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66149@debbugs.gnu.org \
    --cc=Hi-Angel@yandex.ru \
    --cc=juri@linkov.net \
    --cc=stefankangas@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).