GNU bug report logs - #14192
24.3.50; recursive edit while running ispell not working usefully

Previous Next

Package: emacs;

Reported by: michael_heerdegen <at> web.de

Date: Fri, 12 Apr 2013 15:06:01 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 14192 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 14192 <at> debbugs.gnu.org, stefankangas <at> gmail.com
Subject: Re: bug#14192: 24.3.50; recursive edit while running ispell not
 working usefully
Date: Fri, 12 Jan 2024 00:14:56 +0100
Eli Zaretskii <eliz <at> gnu.org> writes:

> He said "if I don't hear from you".  If there's no answer and no new
> information, leaving bugs open just accumulates bugs that are not (and
> cannot be) worked on.

The "cannot be" part is not true in this case.  I provided an easy
recipe, the problem is reproducible in a few seconds.

> So we made a decision to close such bugs.  If the issue still exists
> and affects someone, those persons will probably report it at some
> point with enough information to allow investigating and fixing the
> problem.

And I provided a lot of information, and even an analysis.

> I don't see anything wrong with this policy.

This policy is good, but not appropriate in this case.

> We do know from bitter experience the downsides of not closing such
> bugs -- gobs of open bugs that no one looks at.  That is worse,
> IMNSHO.

That's a big problem, I know about it.  I remember Lars' statistics.

However the other side is also important.  I remember a discussion a
year or so ago, when somebody mentioned something is not working, and a
few people added that it doesn't work for them as well.  Then you
wondered why nobody had created a bug report..

It is important to give the people reporting bugs a good feeling.  The
feedback they get after such a long time should not sound that negative.
Ignored a report for such a long time is not nice, and even if it's not
our fault, we could say that we are sorry about that.  Choosing a more
positive will also raise the chance of a reply.  If this is a standard
text, it might be worth the time to improve it.

Michael.




This bug report was last modified 1 year and 172 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.