bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#70797: [PATCH] Make the Compilation mode recognize non-legacy Kotlin


From: Eli Zaretskii
Subject: bug#70797: [PATCH] Make the Compilation mode recognize non-legacy Kotlin/Gradle errors
Date: Sat, 08 Jun 2024 14:44:31 +0300

Ping! Ping! Can we please resolve this issue?

> Cc: 70797@debbugs.gnu.org
> Date: Sat, 25 May 2024 10:46:53 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> Ping!  Can we please make progress with resolving this issue?
> 
> > Cc: 70797@debbugs.gnu.org
> > Date: Sat, 11 May 2024 11:56:02 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > 
> > > From: Rudolf Adamkovič <rudolf@adamkovic.org>
> > > Date: Mon, 06 May 2024 00:14:04 +0200
> > > 
> > > >From 8ff95a02a321d730e2c3171b18ddb55f3a554d20 Mon Sep 17 00:00:00 2001
> > > From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?= <rudolf@adamkovic.org>
> > > Date: Thu, 2 May 2024 19:06:11 +0200
> > > Subject: [PATCH] Make the Compilation mode recognize non-legacy 
> > > Kotlin/Gradle
> > >  errors
> > > 
> > > The Compilation mode recognizes Kotlin/Gradle errors but only in the old
> > > format.  The new format, which has been in wide use for about a year, is
> > > not supported.  This patch adds support for the new format.
> > > 
> > > * etc/compilation.txt:
> > > (symbols): Add a non-legacy Kotlin/Gradle warning and error.
> > > * lisp/progmodes/compile.el:
> > > (compilation-error-regexp-alist-alist): Rename 'gradle-kotlin' to
> > > 'gradle-kotlin-legacy' and add 'grade-kotlin' that matches errors and
> > > warnings outputted by non-legacy Kotlin/Gradle.
> > > ---
> > >  etc/compilation.txt       | 13 +++++++++++--
> > >  lisp/progmodes/compile.el | 20 +++++++++++++++++---
> > >  2 files changed, 28 insertions(+), 5 deletions(-)
> > 
> > Thanks, but:
> > 
> >   . applying this fails compile-tests in the test suite, so I guess
> >     some adjustment there is also needed;
> >   . you removed the comment with the pointer to kotlin sources, which
> >     might be still useful for the legacy format (unless the URL is no
> >     longer valid), so please restore that if the pointer can still be
> >     useful
> > 
> > Thanks.
> > 
> > 
> > 
> > 
> 
> 
> 
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]