From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: acm@muc.de, schwab@linux-m68k.org, monnier@iro.umontreal.ca,
18577@debbugs.gnu.org
Subject: bug#18577: Regexp I-search: [(error Stack overflow in regexp matcher)]
Date: Sat, 23 Oct 2021 11:39:35 +0300 [thread overview]
Message-ID: <83ee8c5e48.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=13XMNB3gRkAp0D_TE0d1Wa4OGN2y_QPkMKGVLtXiORw@mail.gmail.com> (message from Stefan Kangas on Sat, 23 Oct 2021 01:30:07 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> 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 <eliz@gnu.org> 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.
next prev parent reply other threads:[~2021-10-23 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 8:55 bug#18577: Regexp I-search: [(error Stack overflow in regexp matcher)] Alan Mackenzie
2014-09-28 10:56 ` Andreas Schwab
2014-09-28 12:37 ` Alan Mackenzie
2014-09-28 12:48 ` Andreas Schwab
2014-09-28 17:35 ` Stefan Monnier
2014-11-27 8:44 ` Tassilo Horn
2021-10-23 2:47 ` Stefan Kangas
2021-10-23 7:32 ` Eli Zaretskii
2021-10-23 8:30 ` Stefan Kangas
2021-10-23 8:39 ` Eli Zaretskii [this message]
2021-10-23 9:32 ` Stefan Kangas
2021-10-23 11:27 ` Eli Zaretskii
2021-10-24 22:08 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ee8c5e48.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18577@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).