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#61514: 30.0.50; sadistically long xml line hangs emacs Date: Mon, 20 Feb 2023 14:31:07 +0200 Message-ID: <83zg98v7qs.fsf@gnu.org> References: <87lel0c65v.fsf@everybody.org> <838rgvymcd.fsf@gnu.org> <886c06e50e9cfacb7954@heytings.org> <83h6vixik1.fsf@gnu.org> <886c06e50e707ab83560@heytings.org> <886c06e50e876183758c@heytings.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38140"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mah@everybody.org, 61514@debbugs.gnu.org, monnier@iro.umontreal.ca To: Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 20 13:32:30 2023 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 1pU5LJ-0009hG-8m for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 20 Feb 2023 13:32:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pU5L4-00065V-5S; Mon, 20 Feb 2023 07:32:14 -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 1pU5Ks-00060s-Mb for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 07:32:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pU5Ks-0004WZ-E6 for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 07:32:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pU5Ks-0001AP-1a for bug-gnu-emacs@gnu.org; Mon, 20 Feb 2023 07:32:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 20 Feb 2023 12:32:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61514 X-GNU-PR-Package: emacs Original-Received: via spool by 61514-submit@debbugs.gnu.org id=B61514.16768962734425 (code B ref 61514); Mon, 20 Feb 2023 12:32:02 +0000 Original-Received: (at 61514) by debbugs.gnu.org; 20 Feb 2023 12:31:13 +0000 Original-Received: from localhost ([127.0.0.1]:50817 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU5K3-00019H-02 for submit@debbugs.gnu.org; Mon, 20 Feb 2023 07:31:13 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:55280) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pU5Jy-00018n-5F for 61514@debbugs.gnu.org; Mon, 20 Feb 2023 07:31:09 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pU5Js-0004Qw-33; Mon, 20 Feb 2023 07:31:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=xJPEBVxYQufwxhk/WqbflzM6a3ub656QWpO/Z65nHOc=; b=m5LNQOtsUeFW HlAynaJSuiTNXq8s00I6xG6WnrSGJ5ugnkFmaFReoET1dr2uG/Nom/Y6fJLycewu62xGNRzWapv7j lNcF6G4pnLY8qDbbpx7q0Us7h0CX9laL0RWWQ2lFLHCLM1aQYEu/jqVVoHJFGIeAgi4Db6Hd5or8f q/0ZkI5T7H8CDNg5RNzjmV3b7HaugJsns1veqiOZ/5XiGp3/MOqsHeohn6Q3cSGNHTfhsc3SomsDM YkY3KJeAI/8wBAxW6b1pPlv4r03WvF8xsTiNVyLaXgjvrx2SgmlijHHJwxu2epyrK66Ow3X5/0I7K 6p9QhQbQOsZRGKii9NKdIA==; Original-Received: from [87.69.77.57] (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 1pU5Jr-0003ZV-Ay; Mon, 20 Feb 2023 07:30:59 -0500 In-Reply-To: <886c06e50e876183758c@heytings.org> (message from Gregory Heytings on Sun, 19 Feb 2023 23:58:41 +0000) 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:256151 Archived-At: > Date: Sun, 19 Feb 2023 23:58:41 +0000 > From: Gregory Heytings > cc: mah@everybody.org, 61514@debbugs.gnu.org, > Stefan Monnier > > BTW, this makes me wonder why emacs_re_max_failures is not accessible from > Elisp. I think it would be very useful, if only for debugging purposes. > And perhaps let-binding it to a lower value around some potentially (or > actually) problematic regexps would be a good way to prevent or fix bugs > such as the current one. If we know which regexps cause problems, shouldn't we instead fix those regexps, or change how we use them? For debugging purposes, you can set the value in the debugger after starting Emacs, or with a breakpoint just before calling the problematic code. As you have seen from the history of this value, it's problematic to calculate, and the meaning of the value is not obvious. So exposing this to Lisp would be a rope that's too long to give our users and programmers.