From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30883@debbugs.gnu.org
Subject: bug#30883: 27.0.50; completions-annotations face should not be based on italic by default
Date: Wed, 21 Mar 2018 10:37:49 +0100 [thread overview]
Message-ID: <87po3xhiqa.fsf@gmail.com> (raw)
In-Reply-To: <83po3ylkf8.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 20 Mar 2018 19:35:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Tue, 20 Mar 2018 17:16:37 +0100
>>
>> When using insert-char interactively to insert т (CYRILLIC SMALL
>> LETTER TE), the completions buffer uses the completions-annotations
>> face to display the character after the full unicode name. т is one of
>> those characters for which the italic glyph is very different from the
>> non-italic one (it actually looks like an 'm'), which is highly
>> misleading for the user.
>
> I guess it depends on the default font, because on my system the
> italic glyph looks very reasonably similar to the roman variant.
It does. The following monospace fonts on my system display it as a
slanted 'm': Inconsolata, Libertine, Noto Sans UI, Ubuntu Mono. The
others display it as a slanted т, which is arguably incorrect, but
they outnumber those four by approximately 2:1
>> The easy solution would be to just base the completions-annotations
>> face on the default face, but Iʼm sure thereʼs a historical reason for
>> its existence.
>
> FWIW, I happen to like the typeface we use there, so I think we should
> go to a more boring display only if we have a very good reason.
I donʼt think we have a good reason. Iʼll customise
completions-annotations.
Robert
next prev parent reply other threads:[~2018-03-21 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 16:16 bug#30883: 27.0.50; completions-annotations face should not be based on italic by default Robert Pluim
2018-03-20 17:35 ` Eli Zaretskii
2018-03-21 9:37 ` Robert Pluim [this message]
2021-06-25 14:33 ` Lars Ingebrigtsen
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=87po3xhiqa.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=30883@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).