From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Show all warnings and errors
Date: Sat, 17 Sep 2022 23:03:23 -0400 [thread overview]
Message-ID: <CABgWrqrON4qKFQ-Xy2+txgWmQ1q2rj6vESYPJuQk8gwvvondwg@mail.gmail.com> (raw)
In-Reply-To: <CABgWrqoU8=GG8eAQ4EoJovZh4qBg6dAUnDq-g3aTU2SVdfjQnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
Hello Per,
I started using Kawa for some hacking recently and I'm running into the
same issue here, so I looked up this conversation and set `--max-errors=-1`.
It seems like the number of errors printed is still capped at 20, did this
regress somehow?
Duncan.
On Tue, Jan 1, 2019 at 5:07 PM Duncan Mak <duncanmak@gmail.com> wrote:
> Woohoo, that worked!
>
> On Tue, Jan 1, 2019 at 4:42 PM Per Bothner <per@bothner.com> wrote:
> >
> > On 1/1/19 1:30 PM, Duncan Mak wrote:
> > > It looks like this:
> > >
> https://gist.github.com/duncanmak/38f451c9f26ba0000be38d0bd304313b#file-more-changes
> >
> > Ah - as I suspected, I missed a call to Compilation.maxERrors.
> > Try the attached patch.
> >
> > --
> > --Per Bothner
> > per@bothner.com http://per.bothner.com/
>
>
>
> --
> Duncan.
>
--
Duncan.
next prev parent reply other threads:[~2022-09-18 3:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 23:18 Duncan Mak
2019-01-01 2:12 ` Per Bothner
2019-01-01 2:33 ` Duncan Mak
2019-01-01 2:42 ` Per Bothner
2019-01-01 20:47 ` Duncan Mak
2019-01-01 20:58 ` Per Bothner
2019-01-01 21:16 ` Duncan Mak
2019-01-01 21:24 ` Per Bothner
2019-01-01 21:31 ` Duncan Mak
2019-01-01 21:42 ` Per Bothner
2019-01-01 22:08 ` Duncan Mak
2022-09-18 3:03 ` Duncan Mak [this message]
2022-09-18 19:11 ` Per Bothner
2022-09-18 22:06 ` Duncan Mak
2022-09-19 10:48 ` Per Bothner
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=CABgWrqrON4qKFQ-Xy2+txgWmQ1q2rj6vESYPJuQk8gwvvondwg@mail.gmail.com \
--to=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.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.
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).