From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#18577: Regexp I-search: [(error Stack overflow in regexp matcher)] Date: Sat, 23 Oct 2021 11:39:35 +0300 Message-ID: <83ee8c5e48.fsf@gnu.org> References: <20140928085554.GA3157@acm.acm> <87mw9kt3m7.fsf@igel.home> <20140928123717.GC3157@acm.acm> <87d2afud0p.fsf@igel.home> <83mtn05h7b.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6026"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, schwab@linux-m68k.org, monnier@iro.umontreal.ca, 18577@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 23 10:41:33 2021 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 1meCar-0001Pq-2W for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Oct 2021 10:41:33 +0200 Original-Received: from localhost ([::1]:40582 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1meCap-00088X-2p for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Oct 2021 04:41:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50682) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1meCZO-0007HK-Jr for bug-gnu-emacs@gnu.org; Sat, 23 Oct 2021 04:40:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51014) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1meCZO-00033l-Ag for bug-gnu-emacs@gnu.org; Sat, 23 Oct 2021 04:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1meCZO-0008TY-6Q for bug-gnu-emacs@gnu.org; Sat, 23 Oct 2021 04:40:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 23 Oct 2021 08:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18577 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 18577-submit@debbugs.gnu.org id=B18577.163497840032568 (code B ref 18577); Sat, 23 Oct 2021 08:40:02 +0000 Original-Received: (at 18577) by debbugs.gnu.org; 23 Oct 2021 08:40:00 +0000 Original-Received: from localhost ([127.0.0.1]:34327 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1meCZI-0008TA-Dz for submit@debbugs.gnu.org; Sat, 23 Oct 2021 04:40:00 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53338) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1meCZH-0008Sy-5N for 18577@debbugs.gnu.org; Sat, 23 Oct 2021 04:39:55 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55210) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1meCZ9-0002vT-Fl; Sat, 23 Oct 2021 04:39:47 -0400 Original-Received: from [87.69.77.57] (port=2493 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1meCZ9-00050v-2W; Sat, 23 Oct 2021 04:39:47 -0400 In-Reply-To: (message from Stefan Kangas on Sat, 23 Oct 2021 01:30:07 -0700) 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" Xref: news.gmane.io gmane.emacs.bugs:217960 Archived-At: > From: Stefan Kangas > Date: Sat, 23 Oct 2021 01:30:07 -0700 > Cc: acm@muc.de, schwab@linux-m68k.org, monnier@iro.umontreal.ca, > 18577@debbugs.gnu.org > > Eli Zaretskii writes: > > > If we can give useful advice in PROBLEMS, adding that can never hurt. > > Perhaps we could just say this (which makes it easy to search for as the > headline matches the error message): Thanks, but pointing to bug discussions in PROBLEMS is IMO not useful enough. PROBLEMS is for people who look for quick solutions to their immediate problems, so asking them to wade through discussions by developers is sub-optimal. Would it be possible to copy the relevant recommendations from that discussion to the PROBLEMS entry? If shown in a cookbook manner, that could be very helpful in practice, I think.