From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 18342-done@debbugs.gnu.org
Subject: bug#18342: 24.3.93; jumping to compilation error location gives the wrong column
Date: Wed, 11 Mar 2015 03:19:42 +0300 [thread overview]
Message-ID: <m2r3swz8pt.fsf@fastmail.fm> (raw)
In-Reply-To: <jwvoao6nhgd.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Fri, 06 Mar 2015 12:54:47 -0500")
On 06/03/2015 12:54 -0500, Stefan Monnier wrote:
>> Regarding `compilation-error-regexp-alist', the
>> `compilation-first-column' probably could be there, but then it should
>> be something like `compilation-compiler-var-alist' instead :)
>
> I tend to agree that the "first-column" info should probably be placed
> alongside the regexp (same for compilation-error-screen-columns, BTW).
>
>> There are unclear cases e.g. with maven: what if we use Oracle JDK which
>> outputs columns beginning with 0 and then change to another JDK which
>> outputs beginning with 1? Would maven correct it's output? I doubt so.
>> Then we should have two items in the alist: maven-oracle and maven-smth.
>
> Indeed, there are "hard" cases. Luckily, column positions usually
> aren't so terribly important, so being off by a few chars is annoying
> but bearable.
It's even worse, as I've just discovered: we have a "checkstyle" plugin
for Maven which, yes, checks style. And maven outputs its errors with
differently based column numbers (starting with one). This and javac
invocation happens within one compilation, so it seems currently we have
no way of distinguishing between them and applying different settings.
Anyway, I'm closing this bug for now.
Filipp
prev parent reply other threads:[~2015-03-11 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 10:31 bug#18342: 24.3.93; jumping to compilation error location gives the wrong column Filipp Gunbin
2014-08-28 13:22 ` Stefan Monnier
2015-03-05 23:41 ` Filipp Gunbin
2015-03-06 8:34 ` Eli Zaretskii
2015-03-06 17:54 ` Stefan Monnier
2015-03-11 0:19 ` Filipp Gunbin [this message]
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=m2r3swz8pt.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=18342-done@debbugs.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 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.