From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 38024@debbugs.gnu.org, monnier@iro.umontreal.ca,
kevin.legouguec@gmail.com
Subject: bug#38024: 27.0.50; icomplete sometimes fails to show completions after backward-killing words
Date: Sat, 02 Nov 2019 09:37:52 +0200 [thread overview]
Message-ID: <83o8xuk9tb.fsf@gnu.org> (raw)
In-Reply-To: <8736f7nfki.fsf@gmail.com> (message from João Távora on Sat, 02 Nov 2019 03:05:17 +0000)
> From: João Távora <joaotavora@gmail.com>
> Date: Sat, 02 Nov 2019 03:05:17 +0000
> Cc: 38024@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
>
> João Távora <joaotavora@gmail.com> writes:
>
> > Kevin, you're on the right track. The redisplay thing is not the right
> > fix, indeed. Stefan has a fix for this, which he sent me, but I can't
> > find it now.
> >
> > Anyway, it has to do with avoiding the 'select' event in
> > while-no-input.
>
> Hi Kévin,
>
> In the meantime, I found the patch and pushed it right away. It worked
> better than the redisplay hack I had pushed before.
>
> The commit you want to test with is
> 730e7da7ba6a4b545176ea246653928edb10cff4
The current master displays this warning when byte-compiling
icomplete.el:
ELC icomplete.elc
In end of data:
icomplete.el:669:1:Warning: the function `while-no-input-ignore-events' is not
known to be defined.
while-no-input-ignore-events is not a function, it's a variable.
next prev parent reply other threads:[~2019-11-02 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 21:40 bug#38024: 27.0.50; icomplete sometimes fails to show completions after backward-killing words Kévin Le Gouguec
2019-11-01 23:28 ` João Távora
2019-11-02 3:05 ` João Távora
2019-11-02 7:37 ` Eli Zaretskii [this message]
2019-11-02 11:12 ` João Távora
2019-11-02 13:07 ` Eli Zaretskii
2019-11-03 10:25 ` Kévin Le Gouguec
2021-04-05 20:59 ` Stefan Monnier
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=83o8xuk9tb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38024@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=kevin.legouguec@gmail.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 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).