From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tomas Hlavaty Newsgroups: gmane.emacs.devel Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond Date: Wed, 07 Sep 2022 19:02:14 +0200 Message-ID: <87fsh3f78p.fsf@logand.com> References: <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> <83a67bih0f.fsf@gnu.org> <83tu5jgvfy.fsf@gnu.org> <83sfl3gtah.fsf@gnu.org> <87mtbbyyl1.fsf@logand.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14619"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Yuri Khan , incal@dataswamp.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 07 19:04:56 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 1oVyTw-0003Uw-Ny for ged-emacs-devel@m.gmane-mx.org; Wed, 07 Sep 2022 19:04:56 +0200 Original-Received: from localhost ([::1]:38288 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oVyTv-0004s4-Op for ged-emacs-devel@m.gmane-mx.org; Wed, 07 Sep 2022 13:04:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33064) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oVyRS-000461-H8 for emacs-devel@gnu.org; Wed, 07 Sep 2022 13:02:22 -0400 Original-Received: from logand.com ([37.48.87.44]:41074) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oVyRQ-0006gg-EO; Wed, 07 Sep 2022 13:02:21 -0400 Original-Received: by logand.com (Postfix, from userid 1001) id 2957E1A170C; Wed, 7 Sep 2022 19:02:16 +0200 (CEST) X-Mailer: emacs 28.1 (via feedmail 11-beta-1 I) In-Reply-To: Received-SPF: pass client-ip=37.48.87.44; envelope-from=tom@logand.com; helo=logand.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 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:294855 Archived-At: On Wed 07 Sep 2022 at 12:48, Stefan Monnier wrote: >> No, he said that the generated code is saved automatically in a file and >> if the user puts (some-hypothetical-other-command) in his .emacs >> manually, it will load the saved file. Something like: >> >> (defun some-hypothetical-other-command () >> (or (let ((f "~/.emacs.d/cache/some-hypothetical-other-command.el")) >> (when (file-exists-p f) >> (load f))) >> (generate-and-save-that-slow-code))) > > The problem of course being how to decide when to flush the cache. > By making the system less automatic, we expose enough of it that the > user will obviously know how to "flush the cache" and will hopefully > realize when it might need to be "flushed". What does "less automatic" mean? There are two separate issues: 1) How to update the cache: a) rm ~/.emacs.d/cache/some-hypothetical-other-command.el b) or M-x generate-and-save-that-slow-code 2) When to update the cache. I think this has already been discussed: when the user chooses font with different charset. It seems enough to let the user decide.