From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond Date: Wed, 07 Sep 2022 14:02:56 +0300 Message-ID: <83a67bih0f.fsf@gnu.org> References: <83y1v7w6eu.fsf@gnu.org> <2f302d1c3966849477b3@heytings.org> <83mtbiovzr.fsf@gnu.org> <83a67hq3l7.fsf@gnu.org> <83mtbhneht.fsf@gnu.org> <83czcakqd3.fsf@gnu.org> <87a67dxhfw.fsf@dataswamp.org> <875yi0wzx7.fsf@dataswamp.org> <834jxkk635.fsf@gnu.org> <878rmw8085.fsf@dataswamp.org> <83edwnj4fh.fsf@gnu.org> <87tu5j7tu1.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35268"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Emanuel Berg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 07 13:04:59 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 1oVsra-0008wA-Vb for ged-emacs-devel@m.gmane-mx.org; Wed, 07 Sep 2022 13:04:59 +0200 Original-Received: from localhost ([::1]:34782 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oVsrZ-0000hc-3n for ged-emacs-devel@m.gmane-mx.org; Wed, 07 Sep 2022 07:04:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51218) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oVspx-0008Ae-VM for emacs-devel@gnu.org; Wed, 07 Sep 2022 07:03:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52582) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oVspw-0003WD-F3; Wed, 07 Sep 2022 07:03:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=mwxuxSvrVIq93aJv3ZdMai2Nm/D5bLF1uCGc6Eav2vs=; b=EaXaszfMIVfU hASoL/bx5rRSoHFzE5NdeoZOCSgRXMp3z2gRHLUU1RzA4AhVGOHrKdLASrkfBwA2B06DmYfTqpgYl CgmA0GOiOgHXduy6RZt2gkBg/BVdZ/wyimG7R+K1RLJZ78N+vAhlMVxmqyrTVaQActzr1o808oCIs VADfktcOZ+ZdOzxd5ItNdy7Kuk3S9r44rDSeS6I+05paocUZn74Ki2q+D0x802+BNT8eKfDN4vRv4 Rlv7jlfrejD7XeSSimuyVPC/gN20GhBdOE9hsKUGodqSBV8atv1/cJ9EzHxg+RV/MumOAGKFjql1O fXXJjWcpQfdyRjPbg3j/Pg==; Original-Received: from [87.69.77.57] (port=2198 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oVspu-0000rx-Me; Wed, 07 Sep 2022 07:03:15 -0400 In-Reply-To: <87tu5j7tu1.fsf@dataswamp.org> (message from Emanuel Berg on Wed, 07 Sep 2022 05:21:26 +0200) 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:294822 Archived-At: > From: Emanuel Berg > Date: Wed, 07 Sep 2022 05:21:26 +0200 > > Eli Zaretskii wrote: > > >>> If you followed the discussion, this was explained and > >>> unanimously rejected. > >> > >> Yes, but there is surely a way to get around that, a way > >> that is better > > > > If you know how to get around that, please tell the details. > > In general ... > > Compute f(x) = y > > Store f = ((x y) ... ) somewhere. > > Next time don't compute, search for x, find y? > > Maybe x can be detected automatically, as well? Then the whole > process is automated, and invisible. > > No addition to the user's init files necessary, unless s/he > explicitely wants to recompute, "switch x" to something else, > redefine it, yada yada, that will then use whatever you used, > to do steps 1-2 ... and then THAT will be used with the same > functions because only the data (mapping) has changed. I don't think I follow. What is "x" and what is "y" in this case? And where "somewhere" to store this, except on the user init file? And what is meant by "detect x automatically, as well"? If that is the inability to display certain characters, then that's exactly what the command does, so what is the "automatic" alternative you have in mind? Invoking the command automatically every startup is unacceptably slow, as was already explained. What other ideas are for automatically detecting this? IOW, do you have concrete ideas, or are these just general aspirations? If the latter, then I already considered the possible concrete implementations, and concluded that they will be worse than what was installed.