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: Sat, 10 Sep 2022 18:40:26 +0300 Message-ID: <83o7vn9r11.fsf@gnu.org> References: <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> <83a67bih0f.fsf@gnu.org> <83tu5jgvfy.fsf@gnu.org> <83sfl3gtah.fsf@gnu.org> <83fsh3ghn9.fsf@gnu.org> <87bkroub0v.fsf@dataswamp.org> <83r10kdd68.fsf@gnu.org> <87a6777seb.fsf@dataswamp.org> <83bkrnbux2.fsf@gnu.org> <87pmg3jlyn.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20176"; 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 Sat Sep 10 17:41:50 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 1oX2cA-000552-LV for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Sep 2022 17:41:50 +0200 Original-Received: from localhost ([::1]:39388 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oX2c9-0008U8-8w for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Sep 2022 11:41:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46080) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oX2bA-000787-Uq for emacs-devel@gnu.org; Sat, 10 Sep 2022 11:40:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33386) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oX2b9-0008QD-2X; Sat, 10 Sep 2022 11:40:47 -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=MTxI0nri1JCyCzexr3SQEMKxMHdjgiPpgw0wJvjSgeM=; b=bvqV9ou0SBTp YGQDEZSv2KYwDRpta7qRQCCXVqT6jD3fhPwTT1UF9iEt/g85mIyoAgEaqc+QujswGP8j6IEoiSHkl lLv2zyuZ5waxoHGwxSkOdsr3lTegNwcBv1hHh/FjYqbPa54AAFAqaUJ3w5jppNsFzlgeTBL1o97eo Y/vCdjcr6/4kZgDYVnmejUr0wPFrk/ZWlitf4WRMFsIfo7ymoKch7BS8EThC7aYIW4RpHcm/Ry+Gh n8l/LnYn81mBA9PKrbjNenoY4CdWTx19i6NhNUTUAWJXzmRXrKggahS0qgROWOweUxAZ/pdctQ/4q i+yToe9HhhTd1fZFRWqz+w==; Original-Received: from [87.69.77.57] (port=1845 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 1oX2b8-00038u-IK; Sat, 10 Sep 2022 11:40:46 -0400 In-Reply-To: <87pmg3jlyn.fsf@dataswamp.org> (message from Emanuel Berg on Sat, 10 Sep 2022 17:19:44 +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:295135 Archived-At: > From: Emanuel Berg > Date: Sat, 10 Sep 2022 17:19:44 +0200 > > Eli Zaretskii wrote: > > >> If you store the result of running the program you don't > >> need to execute the program again next time you need the > >> result, instead you search for it and retrieve it, simple > >> as that. > > > > That's what the current implementation does. It just stores > > the results as a (much faster) program to be run at Emacs > > startup time, that's all. AFAIU, your proposal is to store > > just the ranges of problematic characters, which would > > require to run, at Emacs startup time, another program to > > read those ranges and issue the calls that the current > > implementation embeds in the stored results. > > Yes, of course, you need to be able to read the stored result. > > But don't we have that already Have what? > and isn't that much less > expensive than to compute that, optimized or not? > > Also, isn't it easier for the user to have just a > > (setup-chars) > > in the init which would > > 1. look for stored data > 2. (a) use it, if found > 2. (b) compute it, if not found, and store it What would be the purpose of adding a function for code that's supposed to go into the user's init file? > I don't see how that ever can be worse than generating code > the user has to put into her/his file to compute the same > thing every time? The code must be added to the init file, once, anyway. > A cache is better in terms of computing resources, and > requires a less complicated interface for us humans. It isn't a cache.