From: Eli Zaretskii <eliz@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: eric@ericabrahamsen.net, akrl@sdf.org, emacs-devel@gnu.org
Subject: Re: native-comp *Warnings* buffer
Date: Fri, 14 May 2021 09:42:06 +0300 [thread overview]
Message-ID: <83lf8hzuip.fsf@gnu.org> (raw)
In-Reply-To: <p91h7j69hdy.fsf@google.com> (raman@google.com)
> From: "T.V Raman" <raman@google.com>
> Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, Andrea Corallo <akrl@sdf.org>
> Date: Thu, 13 May 2021 19:30:17 -0700
>
> 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.
May I suggest that you report these issues instead of (or in addition
to) working around them in your Emacs? Especially when these problems
are from a development version, we need help from everyone who uses
that version to stabilize it as quickly as possible. We cannot do
that efficiently if people solve the issues privately without telling
us.
TIA.
next prev parent reply other threads:[~2021-05-14 6:42 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 [this message]
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 ` Jump to source of warning was " T.V Raman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lf8hzuip.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=raman@google.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).