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 19:05:35 +0800	[thread overview]
Message-ID: <87a66ul30g.fsf@yahoo.com> (raw)
In-Reply-To: <2b1180d2e5a07d0773c9@heytings.org> (Gregory Heytings's message of "Tue, 20 Sep 2022 08:48:53 +0000")

Gregory Heytings <gregory@heytings.org> writes:

> That question means "Can you please try to reproduce the issue with
> emacs -Q?".  If not, it's probably something that is specific to your
> configuration.

But it used to work.  So this has broken how I work with Emacs, and I
want it changed.

And no, it doesn't happen in emacs -Q.

> There is nothing much different in that message from any other "echo"
> in other Makefiles, and I don't see why a leading indentation could
> change the way a pattern such as "[Makefile:412: advice-on-failure]"
> is detected and fontified.  It seems like a bug somewhere.  If you
> replace dashes with, say, '*', or '.', or numbers like "1." and "2.",
> is your problem solved?

The problem seems to be indentation in the Makefile.

> That's your opinion.  Nobody else said something similar, and I
> disagree. What such an advice should display is a bullet list of
> possible actions, that the use can copy-paste and immediately try.

Nobody else having commented simply means most other people do not think
much about this problem.  I do, and for the simple reason that I could
not easily understand the message printed.

What exactly is the problem with making the message easier to understand
for others, even though you yourself think it is fine?

> That's perhaps correct in a docstring or a manual, but not in a
> terminal, in which capitals and e.g. or colors are commonly used to
> put emphasis on something.

But since no colors are used here, that is besides the point.  Printing
a message like this upon something as simple as a Makefile failing:

  !BEWARE! ...mundane advice..
  !BEWARE! ...mundane advice..
  !BEWARE! ...mundane advice..

amounts to what is considered by normal people as yelling in their
faces, which is not welcome in software, or in real life.



  reply	other threads:[~2022-09-20 11:05 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 [this message]
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=87a66ul30g.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).