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 12:13:04 +0000	[thread overview]
Message-ID: <2b1180d2e5ec9c1f8a54@heytings.org> (raw)
In-Reply-To: <871qs6l0u6.fsf@yahoo.com>


>> Apparently you have a bug in your configuration, why should Emacs be 
>> adapted to circumvent the bug in your configuration?
>
> Why do you jump to the conclusion that it is a bug?
>

I do not jump to a conclusion, I said "apparently".  But you cannot share 
a screenshot, you do not want to share a recipe, it doesn't happen with 
emacs -Q nor with my configuration.  All that is not conclusive, but it 
points to a bug.

>> When say git prints an error message, it's not a paragraph in prose.
>
> The message printed upon compilation failing is not simply an error 
> message, it is detailed advice for the user. Such advice should 
> definitely not be a terse (meaning difficult to understand) bullet list, 
> littered with uses of the second person pronoun.
>

It's a detailed advice, and it's not difficult to understand, it lists a 
few commands that the user might try to use to fix the problem.  It is not 
"littered with uses of the second person pronoun" either, there's a single 
"You" at the beginning (and I don't see what's wrong with that).

>> Do you know other program that prints a paragraph in prose when a 
>> failure occurs?
>
> When git or any other program prints an error message, it generally does 
> not try to tell the user about an elaborate series of steps that could 
> solve the problem.
>

Let's see...

$ git push
fatal: The current branch my-new-branch has no upstream branch.
To push the current branch and set the remote as upstream, use

     git push --set-upstream origin my-new-branch

>> No, these !BEWARE! are like a traffic warning sign.  If the warning 
>> text itself had been written in capitals, that could have been 
>> considered as "yelling".
>
> A speed limit/camera warning is supposed to yell at you, and it doing so 
> is justified.  "!BEWARE!" followed by a mundane warning about git is 
> not.
>

It's not a "mundane" warning, "git clean -fdx" deletes files and they 
cannot be recovered, which is something a non-expert git user might not be 
aware of, so I don't see what's wrong with that warning.

But this isn't leading anywhere, let's agree to disagree.



  reply	other threads:[~2022-09-20 12:13 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 [this message]
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=2b1180d2e5ec9c1f8a54@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).