From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Review request (compilation-error-regexp-alist-alist)
Date: Tue, 29 Oct 2019 02:33:16 +0300 [thread overview]
Message-ID: <m2o8y0jvib.fsf@fastmail.fm> (raw)
In-Reply-To: <jwvk18omtrm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 28 Oct 2019 17:43:23 -0400")
Hi Stefan,
On 28/10/2019 17:43 -0400, Stefan Monnier wrote:
> Could you open a bug report against Kotlin requesting they use
> a standard error format instead of inventing yet another one?
Looks like it's done on purpose. Current source (I refer to it in
comment in patch) is here:
https://github.com/JetBrains/kotlin/blob/master/compiler/cli/src/org/jetbrains/kotlin/cli/common/messages/GradleStyleMessagerRenderer.kt
If I trace back a little, I see this commit made 5 years ago:
https://github.com/JetBrains/kotlin/commit/ffe8ae3840d7b9bdc82170c8181031f05ced68bd,
in which they explicitly set the present format. I don't know why they
did that, and commit message doesn't help.
So probably it's not very promising to file a bug about it.
BTW, kotlin compiler by itself reports more "normal" error messages,
this one-letter-error-type format is for gradle plugin only.
The reason for my patch is that kotlin + gradle is a popular combination
nowadays in java world (not that I like this fact :-) In this course I
also added basic support for gradle in my javaimp package (now on
scratch branch, will merge in elpa master soon).
Thanks,
Filipp
next prev parent reply other threads:[~2019-10-28 23:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 20:50 Review request (compilation-error-regexp-alist-alist) Filipp Gunbin
2019-10-28 21:43 ` Stefan Monnier
2019-10-28 23:33 ` Filipp Gunbin [this message]
2019-10-29 1:13 ` Stefan Monnier
2019-10-29 2:01 ` Filipp Gunbin
2019-10-29 13:17 ` Stefan Monnier
2019-10-29 14:21 ` Filipp Gunbin
2019-10-29 14:51 ` Stefan Monnier
2019-10-29 16:42 ` Filipp Gunbin
2019-10-29 17:14 ` Stefan Monnier
2019-10-29 20:08 ` Filipp Gunbin
2019-10-31 18:28 ` Filipp Gunbin
2019-10-31 22:16 ` Stefan Monnier
2019-11-01 12:24 ` Filipp Gunbin
2019-10-31 2:07 ` Richard Stallman
2019-10-31 12:11 ` Stefan Monnier
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=m2o8y0jvib.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).