Jump to source of warning was Re: native-comp *Warnings* buffer

["T.V Raman" <raman@google.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1383 bytes --]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:


Re the Warnings buffer, would it be possible to add a button that jumps
to the place in the elisp source that produced the warning?

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

-- 

Thanks,

--Raman
7©4 Id: kg:/m/0285kf1  •0Ü8