all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: parlando@intergga.ch
Cc: 67884@debbugs.gnu.org
Subject: bug#67884: 30.0.50; fido-mode errors when case-fold-search is nil
Date: Tue, 19 Dec 2023 09:50:03 +0000	[thread overview]
Message-ID: <CALDnm511S7gP5HeoVJn5h_N8c7oqnX6VEW9o3WJescrHNxGkUg@mail.gmail.com> (raw)
In-Reply-To: <b588e504-fcf6-4ed4-8cce-a8ed1e1ea3bb@intergga.ch>

tags 67884 confirm
thanks

On Mon, Dec 18, 2023 at 8:11 PM parlando--- via Bug reports for GNU
Emacs, the Swiss army knife of text editors <bug-gnu-emacs@gnu.org>
wrote:
>
> Hi,
>
> If global case-fold-search is nil, fido-mode throws errors when typing
> upper case letters or on candidates with upper case letters.
>
> Reproduce with: emacs -Q, then:
>
> (fido-mode 1)
> (toggle-case-fold-search)
>
> ;; then execute:
> ;; M-x <T or t or another pattern>
>
> Which produces messages like:
>  > Error in post-command-hook (icomplete-post-command-hook): (error
> "Internal error: \\`\\(.*?\\)T does not match cpp-parse-edit")
>  > Error in post-command-hook (icomplete-post-command-hook): (error
> "Internal error: \\`\\(.*?\\)t does not match LaTeX-mode")

Thanks.  Reproduced.  I think the error specifically was due to
recent changes in Emacs master.  In Emacs 29, fido-mode doesn't
error, but doesn't respect case-fold-search either.

João





  reply	other threads:[~2023-12-19  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 20:10 bug#67884: 30.0.50; fido-mode errors when case-fold-search is nil parlando--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-19  9:50 ` João Távora [this message]
2023-12-19 10:14   ` João Távora
2023-12-19 19:17     ` parlando--- 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=CALDnm511S7gP5HeoVJn5h_N8c7oqnX6VEW9o3WJescrHNxGkUg@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=67884@debbugs.gnu.org \
    --cc=parlando@intergga.ch \
    /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.