From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?K=C3=A9vin_Le_Gouguec?= Newsgroups: gmane.emacs.devel Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond Date: Fri, 26 Aug 2022 08:52:05 +0200 Message-ID: <87bks77azu.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1489"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:TN7Qeus9tC1aLr9kj5qTBcwYxWc= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 26 08:55:00 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 1oRTF6-0000CI-EM for ged-emacs-devel@m.gmane-mx.org; Fri, 26 Aug 2022 08:55:00 +0200 Original-Received: from localhost ([::1]:57314 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRTF4-0000yN-Ty for ged-emacs-devel@m.gmane-mx.org; Fri, 26 Aug 2022 02:54:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38566) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRTCa-00082P-Ky for emacs-devel@gnu.org; Fri, 26 Aug 2022 02:52:24 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:40392) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRTCX-0003jG-3v for emacs-devel@gnu.org; Fri, 26 Aug 2022 02:52:23 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oRTCR-0007M0-SK for emacs-devel@gnu.org; Fri, 26 Aug 2022 08:52:15 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 5 X-Spam_score: 0.5 X-Spam_bar: / X-Spam_report: (0.5 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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:294131 Archived-At: Richard Stallman writes: > The text-based Linux console is unable to display many Unicode > characters. In Emacs 29, display of undisplayable characters has > changed. It used to show them with a diamond. Now it shows the > unicode character code as hex, preceded by \U. > > I find that change quite inconvenient. It makes the text harder to > read. Showing the codes does no good, since I don't know these codes, > not even for characters I am familiar with. To find out what > character a code represents, I have to use C-u C-x =, just as I did > before. > > I last built the sources in May. Has this changed in a significant > way since then? > > I could not find, in NEWS, anything about this change -- it ought to > be in NEWS . Nor a way to go back to the old > behavior. Is there a way? If not, would people please create a way? > > As a separate question, do users generally like this change? > Would it be better to return to the old diamond method as the default? That brings to mind a discussion in January, where (IIRC; apologies for any inaccuracies) you reported that Emacs degraded to displaying diamonds when it had no glyphs for precomposed Unicode codepoints: While one subthread went into displaying those codepoints with sequences of ASCII characters, another subthread dealt with glyphless-char-display-control; the default value for characters which fall in the 'no-font group were supposed to be handled with the hex-code method, but weren't. Eli fixed that inconsistency: <837dalfp4t.fsf@gnu.org> IIUC this was considered a bugfix, which might explain why NEWS does not mention it? I can't find a way to tweak glyphless-char-display-control to let TTY frames show diamonds again… maybe a new value display method would be needed for that purpose? The 'acronym method could display something useful IIUC, though I don't know what would be the smartest way to fill in char-acronym-table. (Hope I'm not confused and that thread was indeed the source of the change you mention; apologies for the noise if not)