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.help Subject: Re: Weird font problem Date: Thu, 06 Jun 2024 13:13:53 +0300 Message-ID: <861q5aidjy.fsf@gnu.org> References: <86y17jsusk.fsf@fastmail.fm> <86ed9bk1z1.fsf@gnu.org> <868qzjgl6g.fsf@fastmail.fm> <86msnyiqmu.fsf@gnu.org> <86msny1r07.fsf@fastmail.fm> 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="39514"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 06 12:15:06 2024 Return-path: Envelope-to: geh-help-gnu-emacs@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 1sFA9A-000A3T-Pl for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 06 Jun 2024 12:15:04 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sFA8U-0000J1-2i; Thu, 06 Jun 2024 06:14:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sFA8T-0000IM-Bs for help-gnu-emacs@gnu.org; Thu, 06 Jun 2024 06:14:21 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sFA8T-0006Cu-32 for help-gnu-emacs@gnu.org; Thu, 06 Jun 2024 06:14:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=en5GjSZFY7EasX6mqpcJMIVBg0smncFCnteyneRk1jo=; b=EFArMnOAodOCYnA6oSlu /LR9LQrCDSeqSv+JGMeoMKydReYnQD5AVUNAK4n7imr97Gzxqy9Bn0d3UvWPbVT1B8cJ9EhHrt5sw hsOFJcS/ZuqUowgHqzB6ERifI1Lz503jlS5/lEKtKZx/UP3hADzoSDjkwerta+pNQvOn0XfSyvhbd O+UFB92Hbje9JRuS7dvOxADqnNi81hD8Armceh+RiX5XwQ+5Gx6mbF5D9Uk1JZ1HJFY27kuntiJco 56f7IN3AwyaeAxRo9QpZN5RcibVtgqNcyD6sAhl/3rvqUSNVKbMic38VY+ZbzCmpytJHyRsViSRyF Oxw69N6OBG62Ew==; In-Reply-To: <86msny1r07.fsf@fastmail.fm> (message from Joost Kremers on Thu, 06 Jun 2024 09:15:20 +0200) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:146862 Archived-At: > From: Joost Kremers > Cc: help-gnu-emacs@gnu.org > Date: Thu, 06 Jun 2024 09:15:20 +0200 > > > Using set-fontset-font. > > (set-fontset-font nil ?🗎 "Noto Sans Symbols 2:style=Regular") > > makes the character appear (i.e., displayed correctly). > > > So something Vertico does is special, if it has this effect. And the > > fact that you see these characters as hex codes elsewhere basically > > means that you lack a font for displaying these characters reliably. > > So maybe, instead of trying to understand how Vertico succeeds to pull > > this trick, you should find and install a font capable of displaying > > those characters when inserted into a "normal" buffer? > > fc-list suggests I already have: > > ``` > joost@sphinx ~$ fc-list ':charset=01f5ce' > /usr/share/fonts/noto/NotoSansSymbols2-Regular.ttf: Noto Sans Symbols 2:style=Regular > /usr/share/fonts/OTF/Font Awesome 6 Free-Regular-400.otf: Font Awesome 6 Free,Font Awesome 6 Free Regular:style=Regular > /usr/share/fonts/OTF/Font Awesome 6 Free-Solid-900.otf: Font Awesome 6 Free,Font Awesome 6 Free Solid:style=Solid > ``` > > So why isn't Emacs finding it? Emacs uses the first font that seems to support a character, so maybe you have another font that gets in the way? I think we should return to this question after you find which of your customizations triggers the problem.