From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Emacs 28: Specific TTF font gets loaded with font-backend x instead of ftcrhb Date: Sat, 08 Feb 2020 15:50:52 +0200 Message-ID: <831rr5dw77.fsf@gnu.org> References: <87pneu1u9e.fsf@gnu.org> <83mu9ygyi7.fsf@gnu.org> <87imkmi46d.fsf@gnu.org> <83eevagoh8.fsf@gnu.org> <878slh0yr8.fsf@gnu.org> <83y2thezjq.fsf@gnu.org> <87v9okyyt5.fsf@gnu.org> <83pnerfuq1.fsf@gnu.org> <835zgig231.fsf@gnu.org> <87lfpe65my.fsf@gnu.org> <83y2teedbh.fsf@gnu.org> <87v9oh8lkl.fsf@gnu.org> <87r1z58kz6.fsf@gnu.org> <835zghe63z.fsf@gnu.org> <834kw1e57j.fsf@gnu.org> <87mu9t8dok.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="42127"; 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 Sat Feb 08 14:51:35 2020 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 1j0QWE-000ArQ-TP for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 08 Feb 2020 14:51:34 +0100 Original-Received: from localhost ([::1]:41792 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j0QWE-0004N5-0S for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 08 Feb 2020 08:51:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48567) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j0QVr-0004KT-7M for help-gnu-emacs@gnu.org; Sat, 08 Feb 2020 08:51:12 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45413) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1j0QVr-0005Y1-3I for help-gnu-emacs@gnu.org; Sat, 08 Feb 2020 08:51:11 -0500 Original-Received: from [176.228.60.248] (port=2854 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1j0QVq-0004RL-Ih for help-gnu-emacs@gnu.org; Sat, 08 Feb 2020 08:51:10 -0500 In-reply-to: <87mu9t8dok.fsf@gnu.org> (message from Tassilo Horn on Sat, 08 Feb 2020 13:29:47 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.help:122376 Archived-At: > From: Tassilo Horn > Cc: help-gnu-emacs@gnu.org > Date: Sat, 08 Feb 2020 13:29:47 +0100 > > >> We should not signal this error when the unibyte string is > >> pure-ASCII. Let me think of a solution. > > > > Does the below help? > > Yes, it does help. The error is gone. Thanks, I installed it on master, since even though such compositions are undesirable, they are better then an infinite sequence of errors during redisplay. > > If it does, you should see the "--" in the mode line replaced with the > > ligature (whether this is the desired behavior is another question). > > Exactly, and here I'd say it is definitively not the right behavior > because because both chars have a separate meaning (buffer writable? > and buffer modified?) and help-echo which aren't accessible anymore. > > I don't know how to cope with such situations. We could insert a ZWNJ character between the two characters, but that is not a general solution, since mode-line strings can be dynamically consed by applications, and at least the input-method indicator on the mode line must be able to display composed characters. I guess this is something else we should figure out before we can freely use ligatures in Emacs. > Maybe composition should only consider strings with equal text > properties. That already happens, at least with face properties. > Or, as you already said, there should be some text property > inhibiting composition which the mode-line could use. Yes, maybe. Although that, too, could have problems with mode-line strings produced by Lisp programs.