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 16:00:13 +0200 Message-ID: <5CB2325C-0A1E-4AC6-B61E-DFA46F3CFC80@gmail.com> References: <909EF5E1-6F30-4A35-84E8-2EF4333115FD@gmail.com> <4996E536-72CE-4E6A-9C75-CF7307A82469@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="7274"; 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 16:01:21 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 1qolOK-0001j1-Jd for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 06 Oct 2023 16:01:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qolO2-0000Dx-Jr; Fri, 06 Oct 2023 10:01:02 -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 1qolNs-00006E-H8 for bug-gnu-emacs@gnu.org; Fri, 06 Oct 2023 10:00:52 -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 1qolNj-0005Bs-Jh for bug-gnu-emacs@gnu.org; Fri, 06 Oct 2023 10:00:51 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qolO2-0008Ls-4n for bug-gnu-emacs@gnu.org; Fri, 06 Oct 2023 10:01: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 14:01: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.169660084232065 (code B ref 60830); Fri, 06 Oct 2023 14:01:02 +0000 Original-Received: (at 60830) by debbugs.gnu.org; 6 Oct 2023 14:00:42 +0000 Original-Received: from localhost ([127.0.0.1]:52329 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qolNi-0008L6-1q for submit@debbugs.gnu.org; Fri, 06 Oct 2023 10:00:42 -0400 Original-Received: from mail-lj1-x22b.google.com ([2a00:1450:4864:20::22b]:59415) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qolNg-0008Kr-A5 for 60830@debbugs.gnu.org; Fri, 06 Oct 2023 10:00:40 -0400 Original-Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2bffc55af02so25568711fa.2 for <60830@debbugs.gnu.org>; Fri, 06 Oct 2023 07:00:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696600815; x=1697205615; 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=f5DRh7Y7rgYmqrNOr37VmeU9l8dqZ/dB4iGRkKKP8hY=; b=jHcPHzDLkUTyoZbs/tpab4Gf2A6rur7aUq8y0FuuS70vZULtlX5q0qA9FLYMJIsd5L Yimx5ef25/G/W2T+kGq60/tssXjcKoVlBjodZ3rn9WVWD0+CNhleter3FJ4LhX6mvGxq 0MmdnNtj/G/Zrd/Cs9LRaJuL9w2SbcCM2GnEBIM1FyczPB+MJvYxXpe4XpkB7/zImzhY uMbCTwc24uzAoowhS52K8tN8ZKbg6z2iiRdVtHhq6Mrwqwnt94piofyLDk7czNsFgJPN o2B4MlQYAee1+A10EGiucb2jJ5fSKIPKLZg/CaUbW47nrkJzd7MoJ/+109WG4G42aWg1 vang== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696600815; x=1697205615; 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=f5DRh7Y7rgYmqrNOr37VmeU9l8dqZ/dB4iGRkKKP8hY=; b=E3TbDqAVxRyU00oQogD8orpsdLm3nwpEj/xKUwtdPT1hAFD4JjXBPNYZYFPVpiPmzk WChOEBt8L08gGuCY7x1PhlHGsq9TgZbILd+f6xBLRrn2TiP7MWYDOQLqJO7JeH+aAfp9 WINWYrCtJpkIcdHiKmTONgKJeOa5vOWPvF62kQiSWCoTVUrkA6HkfO0OHg+39TOi5sc7 K4IFmAF7cszDiNGZZsTNdc0wTa4yMfTTqgnD56IH5WRBxCU3gSeJ4evqsQbegdFeVIE9 gTnfvX8omGU/xJg/IHQa5o/uGpbQM9I/DrqsllQuctYoiZz0RssueUNigj7ufjaDN/3h C8fQ== X-Gm-Message-State: AOJu0YwHAHzUvbMRMw7J7yZSfG0PwKXxsdK2P/4yKwkcgEHSM1oxM/mv 4gZMWCEcuRT/mnmj74+9b40= X-Google-Smtp-Source: AGHT+IGelWG8OTqHAfisIKBo7mzYfYbnA/CS6jf7FDvxgvmxOi/Z3scfHdf9p522vaFu7C4JKLbUpA== X-Received: by 2002:a05:6512:1390:b0:500:a2d3:3e65 with SMTP id fc16-20020a056512139000b00500a2d33e65mr8359924lfb.23.1696600814594; Fri, 06 Oct 2023 07:00:14 -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 h21-20020a197015000000b004edc72be17csm318730lfc.2.2023.10.06.07.00.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Oct 2023 07:00:13 -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:271950 Archived-At: 6 okt. 2023 kl. 15.21 skrev Stefan Monnier : > Can we rely on the ordering in `compilation-error-regexp-alist` to = give > precedence to the other rules? Currently the ordering in `compilation-error-regexp-alist` (CERA for = short) is the one used, but perhaps you mean the ordering in = `compilation-error-regexp-alist-alist` (CERAA)? I suppose we could compute a permutation of CERA that is consistent with = CERAA and cache it to avoid doing it for every call to = `compilation-parse-errors`, but what to do about non-symbol elements in = CERA? It's easiest to keep letting the user assume responsibility for ordering = CERA correctly if customised. That said, the customisation mechanism = doesn't work well for CERA. Perhaps it would be better to have a list of = desired changes.