Re: native-comp *Warnings* buffer

[Eric Abrahamsen]

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > I think "stealth" compilation performed opportunistically in the
>   > background should indeed not display any warnings (by default).
>
> I understand the reason for saying that, but... would this mean that a
> compilation of that meaterial won't happen later?  Is there a chance
> that you'll never see the warnings that compilation generates?

This wouldn't affect the actual compilation at all. It could affect
whether the user sees the warnings or not, if we default to not popping
up the *Warnings* buffer. They might still go looking for the buffer, or
stumble upon it by accident, though.

I've attached a patch that provides a 'silent option to
`native-comp-async-report-warnings-errors'. In this patch the default is
still t, though we could easily default to 'silent if that seems
desirable.

0001-Provide-a-silent-option-for-native-comp-asyncreport-.patch
Description: Text Data