Re: master 5b3c4004a9 2/2: Remove calls to intern with a static string from code that runs on X

[Gregory Heytings]

> > 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.