unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Gregory Heytings <gregory@heytings.org>
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 16:17:58 +0800	[thread overview]
Message-ID: <87tu52lart.fsf@yahoo.com> (raw)
In-Reply-To: <2b1180d2e5035730c58d@heytings.org> (Gregory Heytings's message of "Tue, 20 Sep 2022 07:55:01 +0000")

Gregory Heytings <gregory@heytings.org> writes:

> I'm puzzled.  Is that with emacs -Q?

No.  I don't develop software in "emacs -Q".

> I'm at 9035c20888, and all links seem to be fontified and to work
> correctly, each one takes me to the right place in the Makefile.  Do
> you have a recipe, perhaps?

The recipe is not very relevant, since we already know the fix.  Which
is to remove indentation and leading dashes from the message.

At the same time, it would be good to remove bullet lists from the
message, and reword it in plain English.  Why?  Because it is easier for
people who, presumably unlike you, are not native English speakers, to
follow instructions laid out in the verbal format they learned at
school, instead of lists of individual, heavily context-dependent
sentences.

Emphasis is better conveyed verbally, rather than with exclamation marks
and capitals.

I think it is also good to remove all uses of the first-person pronoun,
like so:

# ADVICE-ON-FAILURE-BEGIN:all
# Running "make bootstrap" to re-build Emacs without compiled Lisp code
# commonly resolves the problem, while running "make V=1" will cause
# Make to display the commands it invokes to build Emacs, which can help
# investigate the problem.
# ADVICE-ON-FAILURE-END:all

# ADVICE-ON-FAILURE-BEGIN:bootstrap
# Try running "make extraclean" followed by "make", which will rebuild
# Emacs with the default configuration options.  Failing that, run "git
# clean -fdx" and "make bootstrap"; keep in mind that will irretrievably
# delete all files not under version control.  If Emacs still fails to
# build, please report the failure to bug-gnu-emacs@gnu.org, following
# the instructions in the 'Reporting Bugs' node of the Emacs manual.
# ADVICE-ON-FAILURE-END:bootstrap

And this type of build failure should never happen from a tarball, so
the message for both targets should be changed to:

# Please report the build failure to bug-gnu-emacs@gnu.org, following
# the instructions in the 'Reporting Bugs' node of the Emacs manual.

For both targets.



  reply	other threads:[~2022-09-20  8:17 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 [this message]
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
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=87tu52lart.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.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).