From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully Date: Fri, 12 Jan 2024 00:14:56 +0100 Message-ID: <87le8vcvin.fsf@web.de> References: <87hajbkd3v.fsf@web.de> <87ppxzd75p.fsf@web.de> <87mstc5zpt.fsf@web.de> <838r4wmkiy.fsf@gnu.org> Reply-To: Michael Heerdegen Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23129"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 14192@debbugs.gnu.org, stefankangas@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 12 00:15:44 2024 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 1rO4H1-0005l3-To for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 12 Jan 2024 00:15:43 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rO4Go-00034h-IL; Thu, 11 Jan 2024 18:15:30 -0500 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 1rO4GO-0002l6-Te for bug-gnu-emacs@gnu.org; Thu, 11 Jan 2024 18:15:04 -0500 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 1rO4GO-00008M-DZ for bug-gnu-emacs@gnu.org; Thu, 11 Jan 2024 18:15:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rO4GL-0000CJ-NB for bug-gnu-emacs@gnu.org; Thu, 11 Jan 2024 18:15:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 11 Jan 2024 23:15:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14192 X-GNU-PR-Package: emacs Original-Received: via spool by 14192-submit@debbugs.gnu.org id=B14192.1705014882698 (code B ref 14192); Thu, 11 Jan 2024 23:15:01 +0000 Original-Received: (at 14192) by debbugs.gnu.org; 11 Jan 2024 23:14:42 +0000 Original-Received: from localhost ([127.0.0.1]:34281 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rO4G2-0000BB-0A for submit@debbugs.gnu.org; Thu, 11 Jan 2024 18:14:42 -0500 Original-Received: from mout.web.de ([217.72.192.78]:49115) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rO4Fy-0000Aq-Ra for 14192@debbugs.gnu.org; Thu, 11 Jan 2024 18:14:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=s29768273; t=1705014874; x=1705619674; i=michael_heerdegen@web.de; bh=MeTEHfTjdpLOEmzBThM6qdBKXtYxJVvfFwHpRqxrBds=; h=X-UI-Sender-Class:From:To:Cc:Subject:In-Reply-To:References: Date; b=hrBmFGYCm0dhglxFtrOIol9KmcYIJ0pWIXqlH7CM8Yuux6FGi03GpNo1aEQf5EGi L1o1bpt0HoidoQpx9gjgc2JKHf16NPXGYFnfazmvwKJfHYA4+oQLkoZdgcEFTiAXp rwywB/eVrRx5LrC7fd3hlBAr3yx+PBQkwdhXEo5rEA6s/FqfhrtE5yM7qNh5nLcgK boQnxh0tiromPJvYpyS9TUh4hfQOltWTDIRTJfcc18d7UBOgbjgm5oheVeuVNpD/W Gy3sJOgjK++tN8fZJPoQBuiY7wzz+OfsFYohL5e5Tt3y75c53HmTpLVdcBgP/fAkO peM5PXZbgLh9ZUOxAw== X-UI-Sender-Class: 814a7b36-bfc1-4dae-8640-3722d8ec6cd6 Original-Received: from drachen.dragon ([84.59.210.83]) by smtp.web.de (mrweb105 [213.165.67.124]) with ESMTPSA (Nemesis) id 1Ma0Pm-1rcF3u0RbI-00W1U7; Fri, 12 Jan 2024 00:14:34 +0100 In-Reply-To: <838r4wmkiy.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 Jan 2024 08:49:57 +0200") X-Provags-ID: V03:K1:Yf3ytgAHJtrcpcOaKLhegivpJpoF3j5EonD96VnCtLc5FejJZHe j4H6k8F9cGTUXUg8CRJT1bUIS5O89Z/FMZ40VqA4YFmC1Pr3p9nt7NLiNkxX65tBm05BN0d 1x3/i9mXc1RSPSRMGsS9Rpg+GVuLnzTnSByg2R5YKQmNHfGaDsTt6rnShBpcxw+/x9IegYi hfuGTh9qpPDGF05S3IGXA== UI-OutboundReport: notjunk:1;M01:P0:l9eeAdTKu3U=;fFKe3vddgeqaXb4fOypNViVVl1q CRShbqSLtht8LgsEDH+Jqkrb0MTLfOXof9Py2cVK3BM+MxnKys2yp03YIxs+NMA678aDkG8ty K16iZeyHhk+LW7T/rZHwTGzACLppBuaNI+RrMdBak7pjFQ+Bq/tqRCbNE6VJvf+kka+CNaSfA OfClp+f3jC0ipD1WlGPk+I99+eVwM4QpWqzfCBMz/WCHRgzFNCTqmvLNZ5g+AUMLSXPHdscLF Va4NpgmLUQSRENEo/aSIx2Ow29i+DZmxsCoX4fQikr2VtTxLka4NxKTTw5JBFUsYDh5aj1CFD wvSrH1IUfMbACT7+G8j8zE2/AweOMEKOSeDv5fcnkyKiyNsisflWBwiPCpde0cN2q1tFmCt3Y bJZUslbHY/IC4Ub1Z+3ssKqu+9USoKJ2ccz/PcBAEC42/zDnsVn8Trzju0ymy59XvzPFMsTZ/ M1aHatI4JohvLWBE3wpQTCJWfWUmP4XjtDVla2UMkm6Ws7rw//pliuSIdO84bRYnLKYBh1jxq SYfwBcRVhA1dGNqP1pGu17BHJtXSkTdvUJn1cBKb4I2ShGFJ9nYmxBL2jLZgJG2xmF0KlkiDL K4D5qbpCxOPpBcCbdDWRfKpVUKWbMg/A5AizJwCRCbQsUSwJdKMFW2IiNSTCWvrCoem5lyykH 586/cJLVCY4CPdgTfJdwSTR81uwhLXWN4Uq1I7ctSqoXdX8hC63nNObOb9Y47oq9t6HGyesTY xPYEdIIvND/tE+M3Wo4oXq+CoWSCo3e5ZVkDWydT6v9tfWNNDpwAaQQeJ5btuDMPjX0fD9O9 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:277970 Archived-At: Eli Zaretskii 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.