From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel 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 Message-ID: <2b1180d2e5ec9c1f8a54@heytings.org> References: <166355307855.3830.3892166668612546304@vcs2.savannah.gnu.org> <20220919020439.67823C00874@vcs2.savannah.gnu.org> <874jx328ye.fsf@gnus.org> <877d1zsufw.fsf@yahoo.com> <87bkrbredr.fsf@yahoo.com> <878rmfpy2g.fsf@yahoo.com> <87fsgmn8cy.fsf@yahoo.com> <2b1180d2e5035730c58d@heytings.org> <87tu52lart.fsf@yahoo.com> <2b1180d2e5a07d0773c9@heytings.org> <87a66ul30g.fsf@yahoo.com> <2b1180d2e5ee5ff71aa1@heytings.org> <871qs6l0u6.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40351"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 20 16:59:26 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oaeib-000AHw-My for ged-emacs-devel@m.gmane-mx.org; Tue, 20 Sep 2022 16:59:25 +0200 Original-Received: from localhost ([::1]:36292 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oaeia-0006c8-M9 for ged-emacs-devel@m.gmane-mx.org; Tue, 20 Sep 2022 10:59:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56924) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oac7t-00086s-HL for emacs-devel@gnu.org; Tue, 20 Sep 2022 08:13:22 -0400 Original-Received: from heytings.org ([95.142.160.155]:49004) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oac7p-0007db-JX for emacs-devel@gnu.org; Tue, 20 Sep 2022 08:13:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1663675984; bh=RLwoxZc++YEbHm/YZDkOhfORCoo5E/1LSxtYHs7UuRs=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=sGp7uCl6rpM4I4RXUkI3UXUiKVTrYeDB30CZGihhyO1IK0AWfBmWorBwe6azmV/3R B8S5EjMNWeor014UcnnOSkWZfbKnPWQzcEbEj+NMc7zmTWsAD3xd8DilJo4Bs7n/8e Uwvke+Un/VCXmJXqtrCcvKSVr9vdiS8MqhQ8Z7JslnRaeRvPQfuLG7QTfnJQvc75D7 xw8ZxUpoG70aoZpfQRugR6qq2OJGKdzdak7xF/kmjga820fw8UG9I9VnVZtnYQTNpJ wnf/JpwQ7nf4uRUeV4NcGCjUWwl5cKOIgEV4D+RL1lHdsQjBQ69eLFR3OKXa9sceGM 7A9wq5P8v6RNw== In-Reply-To: <871qs6l0u6.fsf@yahoo.com> Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:295808 Archived-At: >> 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.