From: Paul Eggert <eggert@cs.ucla.edu>
To: jan <rtm443x@googlemail.com>
Cc: 41155-done@debbugs.gnu.org
Subject: bug#41155: 26.3; regexp 99% locks up emacs
Date: Wed, 13 May 2020 21:46:49 -0700 [thread overview]
Message-ID: <d6e46e82-e19a-cc07-03f0-e85be5ad26cc@cs.ucla.edu> (raw)
In-Reply-To: <CADJx9LdjbTk2kS+wkL_Yn1cKMsNo8nDgt5H2gDJOQnq-cz8f-g@mail.gmail.com>
On 5/13/20 2:11 AM, jan wrote:
> Would someone consider this closing this issue please?
Sure, done. Thanks for following up.
prev parent reply other threads:[~2020-05-14 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 17:31 bug#41155: 26.3; regexp 99% locks up emacs jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-12 20:56 ` Paul Eggert
2020-05-12 22:28 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-13 9:11 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-14 4:46 ` Paul Eggert [this message]
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=d6e46e82-e19a-cc07-03f0-e85be5ad26cc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=41155-done@debbugs.gnu.org \
--cc=rtm443x@googlemail.com \
/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).