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: Mon, 2 Oct 2023 11:37:37 -0700 [thread overview]
Message-ID: <CADwFkmnL-TyqM_bWumzydpW-ycLFAz1ZddfHiNsH4v8XcE2Peg@mail.gmail.com> (raw)
In-Reply-To: <m2il7ptemm.fsf@me.com>
Rudolf Adamkovič <salutis@me.com> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> 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?
>
> Thank you for the reply, Stefan.
>
> So, we seem to have 2 problems here:
>
> (1) the first line contains a space character after the 'PROGRAM:'
> segment, which Lua developers might be willing to change perhaps,
>
> and
>
> (2) the stack trace lines are indented, which I doubt Lua developers
> would want to change.
>
> Would it make sense to ask Lua developers about fixing (1) only, or
> would fixing (2) in Emacs also "magically" fix (1), if Emacs has to
> handle Lua specifically anyway?
AFAICT, all that is needed is to fix the formatting you describe in (1).
That will give the desired behavior.
Regarding (2), I think compilation-mode already detects those as file
locations, with no changes. At least it does on current master.
next prev parent reply other threads:[~2023-10-02 18:37 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmnL-TyqM_bWumzydpW-ycLFAz1ZddfHiNsH4v8XcE2Peg@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.