From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
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 [thread overview]
Message-ID: <831rr5dw77.fsf@gnu.org> (raw)
In-Reply-To: <87mu9t8dok.fsf@gnu.org> (message from Tassilo Horn on Sat, 08 Feb 2020 13:29:47 +0100)
> From: Tassilo Horn <tsdh@gnu.org>
> 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.
prev parent reply other threads:[~2020-02-08 13:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 11:12 Emacs 28: Specific TTF font gets loaded with font-backend x instead of ftcrhb Tassilo Horn
2020-02-04 12:15 ` Robert Pluim
2020-02-04 12:25 ` Robert Pluim
2020-02-04 12:58 ` Tassilo Horn
2020-02-04 13:54 ` Robert Pluim
2020-02-04 14:21 ` Tassilo Horn
2020-02-04 16:26 ` Robert Pluim
2020-02-04 18:32 ` Tassilo Horn
2020-02-04 20:11 ` Robert Pluim
2020-02-05 16:51 ` Tassilo Horn
2020-02-04 15:31 ` Eli Zaretskii
2020-02-04 18:43 ` Tassilo Horn
2020-02-04 19:08 ` Eli Zaretskii
2020-02-05 16:44 ` Tassilo Horn
2020-02-05 17:04 ` Eli Zaretskii
2020-02-06 7:12 ` Tassilo Horn
2020-02-06 18:15 ` Eli Zaretskii
2020-02-07 9:21 ` Tassilo Horn
[not found] ` <b271f1084b17a53ee1583d1f8cd92e9ed21cf360.camel@gnu.org>
2020-02-07 9:48 ` Eli Zaretskii
2020-02-07 10:41 ` Tassilo Horn
2020-02-07 13:28 ` Eli Zaretskii
2020-02-08 9:39 ` Tassilo Horn
2020-02-08 9:52 ` Tassilo Horn
2020-02-08 10:16 ` Eli Zaretskii
2020-02-08 10:36 ` Eli Zaretskii
2020-02-08 12:29 ` Tassilo Horn
2020-02-08 13:50 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831rr5dw77.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).