From: Eli Zaretskii <eliz@gnu.org>
To: "Robert Pluim" <rpluim@gmail.com>, "João Távora" <joaotavora@gmail.com>
Cc: 72176@debbugs.gnu.org, aqua0210@foxmail.com, visuweshm@gmail.com
Subject: bug#72176: 30.0.60; icomplete-vertical-mode failed to work with Error
Date: Sat, 20 Jul 2024 09:05:16 +0300 [thread overview]
Message-ID: <86wmlgegyr.fsf@gnu.org> (raw)
In-Reply-To: <87h6clc0nu.fsf@gmail.com> (message from Robert Pluim on Fri, 19 Jul 2024 09:15:49 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 72176@debbugs.gnu.org, aqua0210@foxmail.com, visuweshm@gmail.com
> Date: Fri, 19 Jul 2024 09:15:49 +0200
>
> >>>>> On Thu, 18 Jul 2024 18:34:35 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> Eli> (I tested on GNU/Linux as well, and couldn't reproduce.) Why does it
> Eli> happen to you and not to others? What conditions should happen and
> Eli> how to modify the recipe to reproduce this?
>
> If I start emacs from "~", it doesnʼt happen, if I start it from eg
> "~/repos/emacs-30" via "src/emacs -Q" then it does happen.
Thanks. I've applied the trivial band-aid on emacs-30 to avoid the
error in post-command-hook, but the real problem is not in the
function that signals the error, it's in icomplete.el where it calls
the lazy-highlight code. The evidence is that after the fix, the
display shown in those cases that caused the error is not the expected
one, unless you set icomplete-tidy-shadowed-file-names non-nil. It
sounds like the problem happens specifically when the minibuffer text
begins with a "~/" and there's another "~/" later in the minibuffer,
the one the user types: the code probably doesn't expect that.
Adding João, who I think wrote this code.
next prev parent reply other threads:[~2024-07-20 6:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 12:13 bug#72176: 30.0.60; icomplete-vertical-mode failed to work with Error Eason Huang
2024-07-18 12:41 ` Eli Zaretskii
2024-07-18 12:49 ` Visuwesh
2024-07-18 14:34 ` Robert Pluim
2024-07-18 15:34 ` Eli Zaretskii
2024-07-19 7:15 ` Robert Pluim
2024-07-20 6:05 ` Eli Zaretskii [this message]
2024-07-20 9:09 ` João Távora
2024-07-20 10:15 ` Eli Zaretskii
2024-07-20 16:48 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-21 2:27 ` Dmitry Gutov
2024-07-21 21:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 7:31 ` Eli Zaretskii
2024-07-25 12:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-20 10:07 ` Eason Huang
2024-07-20 10:43 ` Eli Zaretskii
2024-07-18 13:11 ` Arash Esbati
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=86wmlgegyr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72176@debbugs.gnu.org \
--cc=aqua0210@foxmail.com \
--cc=joaotavora@gmail.com \
--cc=rpluim@gmail.com \
--cc=visuweshm@gmail.com \
/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.