From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.bugs Subject: bug#60830: 30.0.50; The *Compilation* buffer does not recognize Lua errors Date: Fri, 6 Oct 2023 18:20:45 +0200 Message-ID: <6F3E07C8-3E9E-481C-B89C-7045D1028A2A@gmail.com> References: <909EF5E1-6F30-4A35-84E8-2EF4333115FD@gmail.com> <4996E536-72CE-4E6A-9C75-CF7307A82469@gmail.com> <5CB2325C-0A1E-4AC6-B61E-DFA46F3CFC80@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15820"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 60830@debbugs.gnu.org, Rudolf =?UTF-8?Q?Adamkovi=C4=8D?= , Stefan Kangas To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 06 18:22:08 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 1qonaZ-0003pV-J4 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 06 Oct 2023 18:22:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qonaE-0003w5-5L; Fri, 06 Oct 2023 12:21:46 -0400 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 1qonaC-0003vl-1V for bug-gnu-emacs@gnu.org; Fri, 06 Oct 2023 12:21:44 -0400 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 1qonaB-0005KY-Pb for bug-gnu-emacs@gnu.org; Fri, 06 Oct 2023 12:21:43 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qonaU-0006eR-GP for bug-gnu-emacs@gnu.org; Fri, 06 Oct 2023 12:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 06 Oct 2023 16:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60830 X-GNU-PR-Package: emacs Original-Received: via spool by 60830-submit@debbugs.gnu.org id=B60830.169660927625463 (code B ref 60830); Fri, 06 Oct 2023 16:22:02 +0000 Original-Received: (at 60830) by debbugs.gnu.org; 6 Oct 2023 16:21:16 +0000 Original-Received: from localhost ([127.0.0.1]:52502 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qonZj-0006cc-LB for submit@debbugs.gnu.org; Fri, 06 Oct 2023 12:21:16 -0400 Original-Received: from mail-lf1-x136.google.com ([2a00:1450:4864:20::136]:48631) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qonZh-0006cN-Qk for 60830@debbugs.gnu.org; Fri, 06 Oct 2023 12:21:14 -0400 Original-Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-5044dd5b561so2847115e87.1 for <60830@debbugs.gnu.org>; Fri, 06 Oct 2023 09:20:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696609248; x=1697214048; darn=debbugs.gnu.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date:message-id:reply-to; bh=4qJPN/0p1f3qBXHp8t0WwJDbZWQJfxpFAK7cxffLDn0=; b=RWD0Py2VBqmtaWBgzM76XI7T7ks8DtOTCugUWTJTHNt7MAJeEfCxlG83xCOQS5BCpI Vj0GnlmJtrBu3xl1TP1BES3i53oc6IVTeZ1Q0e6a8OEXqVSLBvrlwdVhIXL/EVM1xRic 8nLb5X8RApWoJQYrcNcpKAC7xXHvRNZL4W0+7ntnweOIGl8Ql2Kw7bEOFUK383MNDfCd 03h+Vjp7ozpQT31EWpa9QGJaR3s/1E1Ep+D4gBSJD3llqHeKTjwoNVMHa2h58JJVvg/D 50z81qu0dRv4RV5ypSuWKLpkOOV+MIhz/AMxKDj2ZaGgofv6GV2Ze59FeC927k4H+mY2 6Swg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696609248; x=1697214048; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4qJPN/0p1f3qBXHp8t0WwJDbZWQJfxpFAK7cxffLDn0=; b=teYwenIjejz4FyOqgySZnTNgm3DiC7gjCStZCJZRJWxznHfSzvdkuZfs00D2ZRtSpt HdB3RuLOGL0u6Z8hmZo97u2r3dLzRUONZXfgaYFncl25S34n++PS8TS8KBcbfYLE2DVX j/dWHM3J9DQfGOonDRilQ4c18YzTfBxSf4HUzLjKpiYe/DyY5Ozm4H/DnPCXnLMvZH7O fobUoS/GrTwmFuuT/p4TKdSLbfdOgFzo3oAs0dEedROmm4fa/T38yyi2etqKeY3QvpfI ye6Tpwlm6PJ5eFmHG0skwb/nt+pqTqoGxOu5ui/TAhdqGOvsSPckgMcvHFD6r7JxcvV4 hQKQ== X-Gm-Message-State: AOJu0YychO/Nws9nLu0vXlJckunp9iDUej0cb3+/yzKg3nf00/0A+txk un8QeI5YkFd+LZNuWsHPSWg= X-Google-Smtp-Source: AGHT+IEXV3xXtlTF5KLpNAliS2XkmDZQuVhVG37dhxwpTfaCSDhA22VVHi9MG7cq+5cgnOoYJFHDyA== X-Received: by 2002:ac2:5f64:0:b0:4fe:347d:7c4b with SMTP id c4-20020ac25f64000000b004fe347d7c4bmr7346074lfc.7.1696609247742; Fri, 06 Oct 2023 09:20:47 -0700 (PDT) Original-Received: from smtpclient.apple (c188-150-165-235.bredband.tele2.se. [188.150.165.235]) by smtp.gmail.com with ESMTPSA id u13-20020ac248ad000000b00504818fcb07sm353762lfg.266.2023.10.06.09.20.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Oct 2023 09:20:47 -0700 (PDT) In-Reply-To: X-Mailer: Apple Mail (2.3654.120.0.1.15) 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:271957 Archived-At: 6 okt. 2023 kl. 16.47 skrev Stefan Monnier : > No, I do mean the ordering in CERA: is there a reason not to use this > ordering to lower the precedence of those Lua rules instead of > disabling them? I'd say keeping rules active but placed where they never or only = sometimes match can be seen as the worst of all choices: there is no = indication that they are essentially inactive but things don't work = right, and they still consume CPU. What about powering ahead in the other direction and disable a whole lot = of rarely-used rules? (No shortage of those.) Perhaps we could make a = nicer interface for discovery and selection of available rules. The = natural way is selecting a subset, not composing a list. The rule names aren't ideal either and tell the user very little. We = could augment each rule with a short description and an example of what = they match, and perhaps information about rules that conflict. > Admittedly, there is a performance cost to having all those big = regexps > active "just in case". =20 Yes, and the number keeps growing so unless we start removing or = disabling ones, it's only getting worse. > I wonder is we could come > with a way to figure out tell tale signs that particular tools might = be > (or can't be) used. I can think of some dodgy heuristics that will make nobody happy but = that's it.