From: "T.V Raman" <raman@google.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Jump to source of warning was Re: native-comp *Warnings* buffer
Date: Sun, 16 May 2021 07:06:04 -0700 [thread overview]
Message-ID: <p91mtsuzsc3.fsf_-_@google.com> (raw)
In-Reply-To: <87y2cfwbz5.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 15 May 2021 21:15:26 -0700")
[-- 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
next prev parent reply other threads:[~2021-05-16 14:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 19:59 native-comp *Warnings* buffer Eric Abrahamsen
2021-05-13 20:20 ` Eric Abrahamsen
2021-05-13 21:28 ` Andrea Corallo via Emacs development discussions.
2021-05-13 21:34 ` Eric Abrahamsen
2021-05-13 22:00 ` Eric Abrahamsen
2021-05-14 6:28 ` Eli Zaretskii
2021-05-14 2:30 ` T.V Raman
2021-05-14 6:42 ` Eli Zaretskii
2021-05-14 6:11 ` Eli Zaretskii
2021-05-14 15:44 ` Eric Abrahamsen
2021-05-14 16:23 ` Stefan Monnier
2021-05-14 16:46 ` Eric Abrahamsen
2021-05-14 16:54 ` Eric Abrahamsen
2021-05-15 5:33 ` Richard Stallman
2021-05-16 4:15 ` Eric Abrahamsen
2021-05-16 14:06 ` T.V Raman [this message]
2021-05-16 20:04 ` Andrea Corallo via Emacs development discussions.
2021-05-16 21:25 ` Eric Abrahamsen
2021-05-17 6:11 ` Andrea Corallo via Emacs development discussions.
2021-05-17 3:23 ` Richard Stallman
2021-05-17 6:16 ` Eli Zaretskii
2021-05-16 5:12 ` Stefan Monnier
2021-05-16 5:30 ` Eli Zaretskii
2021-05-16 6:03 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p91mtsuzsc3.fsf_-_@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.