emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: native-comp-async-report-warnings-errors default value


From: Eli Zaretskii
Subject: Re: native-comp-async-report-warnings-errors default value
Date: Tue, 07 Dec 2021 16:28:22 +0200

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,  Eli Zaretskii <eliz@gnu.org>,
>   Stefan Kangas <stefankangas@gmail.com>,  emacs-devel@gnu.org
> Date: Tue, 07 Dec 2021 13:38:01 +0100
> 
> >>>>> On Tue, 07 Dec 2021 09:54:12 +0000, Andrea Corallo <akrl@sdf.org> said:
> 
>     Andrea> Robert Pluim <rpluim@gmail.com> writes:
>     >>>>>>> On Tue, 07 Dec 2021 09:37:30 +0000, Andrea Corallo <akrl@sdf.org> 
> said:
>     >> 
>     Andrea> What is the problem with changing it after pretest is done?
>     >> 
>     Andrea> In the Emacs world by definition there's no clear distinction 
> between
>     Andrea> users and developers, postponing the switch we maximize the 
> probability
>     Andrea> that some user/developer fix some broken code no?
>     >> 
>     >> Are there clear instructions somewhere mapping from the warnings to
>     >> the changes required in the 'broken code'? (I wouldnʼt call it 'broken'
>     >> if it works in current Emacs)
> 
>     Andrea> The docstring of `native-comp-async-report-warnings-errors' itself
>     Andrea> mention the tipical reason of this and its classical fix.  It 
> might be
>     Andrea> mentioned elsewhere tho, not sure.
> 
> Itʼs not in the elisp manual. I think the docstring of
> `native-comp-async-report-warnings-errors' is also not discoverable
> from the *Warnings* buffer, from what I remember.

We can always improve the documentation in this area.  Feel free to
propose a patch, or explain what needs to be improved there, so that
someone else could do it.

TIA



reply via email to

[Prev in Thread] Current Thread [Next in Thread]