unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Weird font problem
Date: Thu, 06 Jun 2024 13:12:25 +0200	[thread overview]
Message-ID: <865xum1g12.fsf@fastmail.fm> (raw)
In-Reply-To: <861q5aidjy.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Jun 2024 13:13:53 +0300")

On Thu, Jun 06 2024, Eli Zaretskii wrote:
> 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.

The culprit seems to be the orderless package.

Starting Emacs with:

```
emacs -Q -L .emacs.d/elpa/compat-29.1.4.5 -L .emacs.d/elpa/vertico-20240511.2047/ -L .emacs.d/elpa/orderless-20240401.959/
```

Then in e.g., *ielm*, execute the following Lisp code reproduces the problem for
me:

```
ELISP> (require 'vertico)

ELISP> (vertico-mode)

ELISP> (setq completion-styles '(orderless basic))

ELISP> (setq completion-category-defaults nil)

ELISP> (require 'orderless)
```

At this point, when I do 'C-x 8 RET' and type 'docu', I see the effect: the
highlighted candidate has the hex box, the other candidates show the correct
glyph.

Orderless does define some faces, but I don't have time right now to dig
further. Loading orderless without vertico doesn't seem to exhibit the problem,
though. (That is, 'C-x 8 RET docu TAB' shows five candidates, but all are
displayed as hex boxes.)


-- 
Joost Kremers
Life has its moments



  reply	other threads:[~2024-06-06 11:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  7:39 Weird font problem Joost Kremers
2024-06-05 12:28 ` Eli Zaretskii
2024-06-05 20:59   ` Joost Kremers
2024-06-06  5:31     ` Eli Zaretskii
2024-06-06  7:15       ` Joost Kremers
2024-06-06 10:13         ` Eli Zaretskii
2024-06-06 11:12           ` Joost Kremers [this message]
2024-06-15  8:26             ` Eli Zaretskii
2024-06-17  8:16               ` Robert Pluim

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=865xum1g12.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=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).