unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: eric@ericabrahamsen.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: native-comp *Warnings* buffer
Date: Mon, 17 May 2021 09:16:28 +0300	[thread overview]
Message-ID: <83tun1ubpf.fsf@gnu.org> (raw)
In-Reply-To: <E1liTqw-0007I5-Dx@fencepost.gnu.org> (message from Richard Stallman on Sun, 16 May 2021 23:23:34 -0400)

> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 16 May 2021 23:23:34 -0400
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
> If you were going to have a compilation of foo.el based on some
> explicit request, and therefore see its warnings then,
> anything that compiles it by anticipation
> and does not show you its warnings
> could cause that explicit request NOT to compile it
> (because it was compiled recently), and therefore you
> would never see its warnings.

I don't think I understand the scenario you described.  Could you
perhaps describe it in simpler terms, like

  . user does A
  . Emacs does X and shows Y
  . user does B
  . emacs shows Z

etc.?

I'm asking because I'd like to figure out what we currently do in this
situation, and how this discussion could affect that.

Thanks.



  reply	other threads:[~2021-05-17  6:16 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           ` 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 [this message]
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=83tun1ubpf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    /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).