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: 1762 bytes --]

Andrea Corallo via "Emacs development discussions."
<emacs-devel@gnu.org> writes:


Lacking a better solution, I implemented myself an after advice on
display-warning that buries the buffer and produces a soft sound to let
me know that a warning got added; then I just go visit that buffer when
I have some cycles to see what raised the warning, and whether it is in
my code, how to fix it etc.

One issue with the warnings is that the reported line  that triggered
the warning tends to  be one or two indirections removed (eg via require
 etc) which makes finding the actual cause fairly  difficult for now > Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> I understand the utility of having these warnings, but does the buffer
>>> need to be popped up every thirty seconds? Couldn't it just be displayed
>>> once, when it's created, and then left alone? Compilation has been going
>>> on for several minutes since rebuilding Emacs, and it's actually hard to
>>> use with *Warnings* occupying my other window every few seconds!
>>
>> I should say that I know about
>> `native-comp-async-report-warnings-errors', and I'd actually like to see
>> these warnings (as many of them are about my own code :(), I'd just like
>> to have them in the background.
>
> Hi Eric,
>
> unfortunately new warnings are showed when they are found while
> compiling.  I agree this is annoying but at the same time I'm not sure
> this behavior wrong.
>
> Anyway in comp.el we just call `display-warning'.  If there's a better
> way to handle this any suggestion or patch is very welcome :)
>
> Thanks
>
>   Andrea
>

-- 

Thanks,

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