From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id wGnSMG8RzmJRIwAAbAwnHQ (envelope-from ) for ; Wed, 13 Jul 2022 02:27:27 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id mKaoMG8RzmKEcwEAauVa8A (envelope-from ) for ; Wed, 13 Jul 2022 02:27:27 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 472102991E for ; Wed, 13 Jul 2022 02:27:27 +0200 (CEST) Received: from localhost ([::1]:52666 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oBQDt-0003uP-FJ for larch@yhetil.org; Tue, 12 Jul 2022 20:27:25 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:39928) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oBQDT-0003uG-EK for emacs-orgmode@gnu.org; Tue, 12 Jul 2022 20:26:59 -0400 Received: from mail-pf1-f176.google.com ([209.85.210.176]:39806) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oBQDS-0003dX-0k for emacs-orgmode@gnu.org; Tue, 12 Jul 2022 20:26:59 -0400 Received: by mail-pf1-f176.google.com with SMTP id j3so8858823pfb.6 for ; Tue, 12 Jul 2022 17:26:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oSbuv1jxNrVKwnfuy9Epvyxz06HGRsBJKkEvejasFgA=; b=xPKz1vNr0FIq6797N2XhcvVCME6yxr1qUpcTmgzDORJ/YOcz61rPBjuQ5TDIeqeB1t skykpxAQcU7m3aoeICM9NhwonEToyAx64taMrKCv6b2s0hapWlk6auAgxUDlMqVy1xFX JuxtjmgNae8IcFMLNaCq4sfWSa3f2L83sHwrPYFyC8A9Mk4/YMCYcNjre6mxY9itWbF/ xNIWXr+TzcGki8CLrP+sG6W+RvpEvljtL+vX1tZIwgYVZs2ZEHAJrhalci+gFSzeuMK/ 67HJkwTPfiRuxeEsMwvON4ndRW1iq2PmeD8imqEG/MJ+r+LyHil+pC/5lhVIfhgtBXi+ Z8Ow== X-Gm-Message-State: AJIora+4geDQV/1gDueZYSKAb7VlWXESWa1bitCVezOx2RTRSkYxmFEr AII57iVwqsTf8Fi67bmqEGmqXhok98LZyS3UKqs= X-Google-Smtp-Source: AGRyM1vFDkSWbhr+oQElZ8ZaLxb4ax+KLUnms6inBNYYAPqFwVGn1cW0B07CyVWWHZhQlWhAZUkkGy+wYU3+5M+m2WQ= X-Received: by 2002:a63:ed48:0:b0:40d:9866:6834 with SMTP id m8-20020a63ed48000000b0040d98666834mr743878pgk.324.1657672016391; Tue, 12 Jul 2022 17:26:56 -0700 (PDT) MIME-Version: 1.0 References: <27918f90-4a82-9f70-611e-7fc5475e2e60@oracle.com> <87r12qyzzb.fsf@posteo.net> <87v8s2xg5d.fsf@posteo.net> <87h73mxfnh.fsf@posteo.net> <80a8e4c8-87cf-245a-57a4-c77c19017507@oracle.com> <87mtddhprr.fsf@localhost> In-Reply-To: <87mtddhprr.fsf@localhost> From: Stefan Kangas Date: Wed, 13 Jul 2022 02:26:45 +0200 Message-ID: Subject: Re: [External] : Re: missing a character / font in agenda? To: Ihor Radchenko Cc: Daniel Ortmann , =?UTF-8?Q?Juan_Manuel_Mac=C3=ADas?= , orgmode Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=209.85.210.176; envelope-from=stefankangas@gmail.com; helo=mail-pf1-f176.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1657672047; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=oSbuv1jxNrVKwnfuy9Epvyxz06HGRsBJKkEvejasFgA=; b=RDYmILs8i9DSscDkuQFpf6kSKvWumLPRr8wE5NksD6P6+UF1OR781aoHfj7Hize1Pxncr9 hUF5O1+aPrvCVwG+fkD7N5e/JMXzQqNqj2qcAZheVcBymVbRhAcN7BdXqeeyUMmZdMfJ5W jp8tIpX7hlW2t7J+MeKRV9yHZVah230Fdti3k/P9k6S8BGXyIxGusy1Bda9RtPPdTjZ+ua lYrl8hWN4dfBOJgQEfc6ThnwU1vGOh7bUXemOtapmGSjuEphIrZtEN/CxR5DkLv1ik100w GTTLTb5eo/KRer22jh0+YBHo/f+AVWUezkaWQfSWoVS0r/QmcOsCQNtzJc3S+A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1657672047; a=rsa-sha256; cv=none; b=NSbIG5RSsRMoLmlKWav2CIpf+qq6huZxWWyydmq50CWLrY2zhzxT5iDkHGj7P2c55283Ry fjKpaueqEKbCzgMZBknNMaUqZkkgEwB3c7NqjDNfYRKrfzsJGF7nYFqv9Dl3zPJhjOy+Mf dDS7tz5z4RsBg5utyIlxsaxPrVdaxh9PAEfPbhPCGiyuySXlljlIQgqz25EtG16ieIGmzP lSCnd/gOGxAot1qYmvqJIy7KdMqSzN4nUHxMzYXY33IUrF5CiVKvt3jDbwPL56Ph6u5sx4 aqlcAlhcZvk+YRnidi8tIhvwefRQa1g+VUi8hZ/OFluMIUA+Mrl8d5SWX/fUOg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -1.75 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 472102991E X-Spam-Score: -1.75 X-Migadu-Scanner: scn1.migadu.com X-TUID: QEDBeXzVyd+E Ihor Radchenko writes: >>> I think this should be considered a bug, since the glyph used (LEFTWARDS >>> TRIANGLE-HEADED ARROW / #2b60) is not present in most fonts. If that is true (I don't know) then maybe we should just use a more ubiquitous glyph? > The commit is supposed to fall back to ASCII symbol if the Unicode > variant is not available, but apparently the check failed for some > reason: [...] > Stefan, do you have any idea what can go wrong here? > > The only thing I can think about is warning in the char-displayable-p > docstring: > > >> On a multi-font display, the test is only whether there is an > >> appropriate font from the selected frame's fontset to display > >> CHAR's charset in general. Since fonts may be specified on a > >> per-character basis, this may not be accurate. I don't think we specify a particular font here, do we? So it seems like there might be a bug in Emacs here? I'm not an expert on this stuff by any means, but I would probably 'M-x report-emacs-bug' to find out why 'char-displayable-p' would say that a character is displayable when it's not.