Re: native-comp *Warnings* buffer

[Richard Stallman <rms@gnu.org>]

[[[ 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. ]]]

  > 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.

Yes, that's exactly the issue.

If you were going to have a compilation of foo.el based on some
explicit request, and therefore see its warnings then,
anything that compiles it by anticipation
and does not show you its warnings
could cause that explicit request NOT to compile it
(because it was compiled recently), and therefore you
would never see its warnings.

Most of the time this would not matter at all.
However, on rare occasions it could cause a real problem.
Perhaps even a serious one.

So I think it is important to make sure this scenario -- suppressing
a warning you would have been shown -- cannot happen.

There are many ways to do that.  My concern is simply that it be done,
one way or another.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)