all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Konstantin Kharlamov <Hi-Angel@yandex.ru>
Cc: 66149@debbugs.gnu.org, juri@linkov.net
Subject: bug#66149: Mistyping a search breaks keyboard macro
Date: Sat, 23 Sep 2023 05:56:10 -0700	[thread overview]
Message-ID: <CADwFkm=-XhOMVhChmWG==QcQ=0=kaBdRftY7hm3jV5HhYxrnkw@mail.gmail.com> (raw)
In-Reply-To: <8334z55ls0.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> 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?

No, I agree with you.  Keeping bugs open when there's no expected
progress typically leads to us forgetting about it, and then one of us
have to come back to close it later anyways.

I think it makes sense to revisit this if/when someone comes up with a
patch, either by reopening this bug, or in a new bug report.





      parent reply	other threads:[~2023-09-23 12:56 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
2023-09-23  8:43             ` Konstantin Kharlamov
2023-09-23  8:58               ` Eli Zaretskii
2023-09-23 12:56             ` Stefan Kangas [this message]

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

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

  git send-email \
    --in-reply-to='CADwFkm=-XhOMVhChmWG==QcQ=0=kaBdRftY7hm3jV5HhYxrnkw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=66149@debbugs.gnu.org \
    --cc=Hi-Angel@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.