all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 14192@debbugs.gnu.org
Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully
Date: Thu, 11 Jan 2024 12:35:11 -0800	[thread overview]
Message-ID: <CADwFkmnBzKtqDaR8X9hVR4+jT+5g1aYz5a9L7i=Uv+O3BkWc3A@mail.gmail.com> (raw)
In-Reply-To: <87mstc5zpt.fsf@web.de>

Michael Heerdegen <michael_heerdegen@web.de> writes:

>> That was 10 years ago, so I'm reaching out to see if this is still
>> an issue on a modern version of Emacs.
>
> AFAIK, nothing has changed in the behavior since then.
> I guess the authors did not intend the recursive edit to be used to
> change the buffer text.
> But if somebody uses it to change the buffer text, Emacs will happily
> mess it up.

OK, thanks.

>> If I don't hear back from you within a couple of months, Ill just assume
>> that this has been fixed and close this bug.
>
> I hope this is not your standard reply.  I mean, ten years, I could have
> died in the meantime, which would not mean that the bug has magically
> disappeared.  I hope you send this kind of text only to people you know
> that are still using Emacs regularly.  Because, if some user asks a
> question, gets no answer, then makes a bug report, and is ignored for
> ten years, it is very unfriendly to request anything at all.  I
> know about the situation of our bug collection, but this is not
> expedient.  You can't expect anyone to even still use Emacs after
> a whole decade.

Yes, this is my standard reply, and yes, if the bug reporter stops
responding, we sometimes just close the bug outright.

I'm not unsympathetic to your position, but please understand that we
have a very limited amount of resources given the tremendous stream of
incoming bugs and improvements that we have to manage.

If we don't sometimes do things summarily, maintaining Emacs will
quickly become an impossible task.  The only alternative I see is that
we simply stop caring about the number of open bugs in the bug tracker,
and then in another 5-10 years or so we nuke it from orbit and start a
new one.  That would lose even more information, but it's not like the
prospect does not sometimes sound pretty appealing.

So do tell us if we make mistakes, but please be patient with us if we
aren't always as polite or diligent as we are on our best days.

Or, even better, volunteer more time to help us fix the bugs.





  parent reply	other threads:[~2024-01-11 20:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 15:00 bug#14192: 24.3.50; recursive edit while running ispell not working usefully Michael Heerdegen
2013-04-12 16:51 ` Michael Heerdegen
2024-01-10 11:19   ` Stefan Kangas
2024-01-11  3:13     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11  6:49       ` Eli Zaretskii
2024-01-11 23:14         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13  7:57           ` Stefan Kangas
2024-01-14  1:13             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 20:35       ` Stefan Kangas [this message]
2024-01-11 23:30         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12  7:44         ` Eli Zaretskii
2024-01-14  1:25           ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  6:29             ` Eli Zaretskii
2024-01-16 19:23               ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 19:28                 ` Eli Zaretskii
2024-01-27  9:09               ` Eli Zaretskii

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='CADwFkmnBzKtqDaR8X9hVR4+jT+5g1aYz5a9L7i=Uv+O3BkWc3A@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=14192@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.