unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: master 5b3c4004a9 2/2: Remove calls to intern with a static string from code that runs on X
Date: Tue, 20 Sep 2022 14:18:03 +0000	[thread overview]
Message-ID: <2b1180d2e53a4f676524@heytings.org> (raw)
In-Reply-To: <87sfkmjjr5.fsf@yahoo.com>


>
> What "emacs -Q" does is not the only correct behavior out there, is it?
>

It isn't, but what we ask to anyone who reports a bug is to provide a 
minimal recipe starting with emacs -Q.  I don't see why the problem you 
see would be different.

Anyway, I've now changed the way the message is displayed, it now uses 
three leading stars and is redirected to stderr, which is e.g. what the 
Linux kernel uses.  Does that fix your problem?

>
> Once again, you (being a native English speaker) may not find it 
> difficult to understand, but I do, and probably many other people who 
> grew up where I did.
>

I guess it's a matter of taste.  To me this (which is the only message 
that most people will ever see):

"make all" failed with exit status 2.
You might try to:
- run "make bootstrap", which might fix the problem
- run "make V=1", which displays the full commands invoked by make,
   to further investigate the problem

immediately tells me that there is a build failure, and that I have two 
options: "make bootstrap" to try to fix the problem, and "make V=1" to 
investigate the problem.  What is unclear to you in that message?



  reply	other threads:[~2022-09-20 14:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166355307855.3830.3892166668612546304@vcs2.savannah.gnu.org>
     [not found] ` <20220919020439.67823C00874@vcs2.savannah.gnu.org>
2022-09-19  6:07   ` master 5b3c4004a9 2/2: Remove calls to intern with a static string from code that runs on X Lars Ingebrigtsen
2022-09-19  6:45     ` Gregory Heytings
2022-09-19  6:53       ` Lars Ingebrigtsen
2022-09-19  7:18       ` Po Lu
2022-09-19  7:42         ` Gregory Heytings
2022-09-19  7:51           ` Po Lu
2022-09-19  7:58             ` Gregory Heytings
2022-09-19  8:01               ` Po Lu
2022-09-19  8:04               ` Gregory Heytings
2022-09-19  8:28                 ` Po Lu
2022-09-19  8:32                   ` Gregory Heytings
2022-09-20  1:27                     ` Po Lu
2022-09-20  7:55                       ` Gregory Heytings
2022-09-20  8:17                         ` Po Lu
2022-09-20  8:48                           ` Gregory Heytings
2022-09-20 11:05                             ` Po Lu
2022-09-20 11:24                               ` Gregory Heytings
2022-09-20 11:52                                 ` Po Lu
2022-09-20 12:13                                   ` Gregory Heytings
2022-09-20 12:46                                     ` Po Lu
2022-09-20 14:18                                       ` Gregory Heytings [this message]
2022-09-21  2:14                                         ` Po Lu
2022-09-21  8:39                                           ` Gregory Heytings
2022-09-21  8:46                                             ` Emanuel Berg
2022-09-21 10:53                                             ` Po Lu
2022-09-21 11:01                                               ` Gregory Heytings
2022-09-21 11:46                                                 ` Po Lu
2022-09-21 14:30                                                   ` Gregory Heytings
2022-09-22  2:47                                                     ` Po Lu
2022-09-22  5:10                                                       ` Eli Zaretskii
2022-09-20 14:16                               ` Eli Zaretskii
2022-09-19  8:27               ` Po Lu

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=2b1180d2e53a4f676524@heytings.org \
    --to=gregory@heytings.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).