From: Stefan Kangas <stefankangas@gmail.com>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 60830@debbugs.gnu.org
Subject: bug#60830: 30.0.50; The *Compilation* buffer does not recognize Lua errors
Date: Wed, 13 Sep 2023 07:55:30 -0700 [thread overview]
Message-ID: <CADwFkmkkG4Q=ROM8U01CjgqP1p_iJ5xjNDsVhR6-29O9imzw4g@mail.gmail.com> (raw)
In-Reply-To: <m2tu0s6nhg.fsf@me.com> ("Rudolf Adamkovič"'s message of "Sun, 15 Jan 2023 12:33:47 +0100")
Rudolf Adamkovič <salutis@me.com> writes:
> REPRODUCTION STEPS:
>
> 1. Write the following in some buffer:
>
> /usr/bin/lua: database.lua:31: assertion failed!
> stack traceback:
> [C]: in function 'assert'
> database.lua:31: in field 'statement'
> database.lua:42: in field 'table'
> database.lua:55: in field 'row'
> database.lua:63: in field 'value'
> database.lua:68: in main chunk
> [C]: in ?
>
> 2. Enable the `compilation-mode'.
>
> EXPECTED:
>
> The Compilation mode recognizes the following as error loci:
>
> - database.lua:31: (twice)
> - database.lua:42:
> - database.lua:55:
> - database.lua:63:
> - database.lua:68:
>
> ACTUAL:
>
> The Compilation mode finds no error loci.
>
> NOTES:
>
> The source files can any extension, such as `fnl' for Fennel.
This breaks because it doesn't follow the GNU standard's
[PROGRAM:]FILE:LINE: MESSAGE
Any chance we could get the lua developers to follow that format,
instead?
See also:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58984#26
next prev parent reply other threads:[~2023-09-13 14:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 11:33 bug#60830: 30.0.50; The *Compilation* buffer does not recognize Lua errors Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 14:55 ` Stefan Kangas [this message]
2023-10-02 12:04 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-02 18:37 ` Stefan Kangas
2023-10-03 8:12 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-03 9:37 ` Stefan Kangas
2023-10-03 20:03 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-05 11:27 ` Mattias Engdegård
2023-10-05 16:21 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 11:38 ` Mattias Engdegård
2023-10-06 13:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 14:00 ` Mattias Engdegård
2023-10-06 14:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 16:20 ` Mattias Engdegård
2023-10-06 16:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-07 11:18 ` Mattias Engdegård
2023-10-07 15:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-08 10:45 ` Mattias Engdegård
2023-10-08 14:47 ` Mattias Engdegård
2023-10-07 21:02 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-08 9:59 ` Mattias Engdegård
2023-10-12 8:12 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 8:17 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 14:32 ` Mattias Engdegård
2023-12-10 22:53 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 13:48 ` Stefan Kangas
2024-01-10 16:37 ` Mattias Engdegård
2024-01-10 17:09 ` Stefan Kangas
2024-01-10 17:45 ` Mattias Engdegård
2023-10-08 15:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 8:14 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkmkkG4Q=ROM8U01CjgqP1p_iJ5xjNDsVhR6-29O9imzw4g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=60830@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=salutis@me.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).