From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Mauro Aranda <maurooaranda@gmail.com>
Cc: 69501@debbugs.gnu.org
Subject: bug#69501: 30.0.50; customize-mode error with substring completion style
Date: Mon, 04 Mar 2024 15:16:12 +0200 [thread overview]
Message-ID: <86frx6m92b.fsf@gnu.org> (raw)
In-Reply-To: <m1h6hpxb3v.fsf@dazzs-mbp.home> (bug-gnu-emacs@gnu.org)
> Date: Sat, 02 Mar 2024 09:59:48 +0100
> From: Eshel Yaron via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> With both Emacs 29.2 and with the current master:
>
> 1. emacs -Q
> 2. (setq completion-styles '(substring))
> 3. C-u M-x customize-mode TAB
> 4. "Assertion failed: (stringp suffix)"
>
> I not sure exactly why this error occurs, but IIUC it has to do with the
> fact that customize-mode let-binds completion-regexp-list. I suspect
> that the substring completion style doesn't handle that correctly.
>
> In general, let-binding completion-regexp-list around completing-read is
> not a great idea IMO because it affects recursive minibuffers as well.
> So perhaps the best solution is to avoid doing that in customize-mode,
> and to rely only on the predicate argument of completing-read instead?
Stefan and Mauro, any suggestions?
next prev parent reply other threads:[~2024-03-04 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 8:59 bug#69501: 30.0.50; customize-mode error with substring completion style Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 13:16 ` Eli Zaretskii [this message]
2024-03-05 12:36 ` Mauro Aranda
2024-03-14 8:26 ` Eli Zaretskii
2024-03-14 18:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 2:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86frx6m92b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69501@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
--cc=me@eshelyaron.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.