From: Eli Zaretskii <eliz@gnu.org>
To: Simon Manning <simon@ecksd.com>, Eason Huang <aqua0210@foxmail.com>
Cc: 67527@debbugs.gnu.org
Subject: bug#67527: 30.0.50; FR: Add an option to disable ispell completion in text-mode
Date: Tue, 09 Jan 2024 15:33:48 +0200 [thread overview]
Message-ID: <83jzoipr5v.fsf@gnu.org> (raw)
In-Reply-To: <CAD9Vh1=tMKpWK19VUAeaYcs-uMG1QRT=4OUF3rkHGVFADWyGfA@mail.gmail.com> (message from Simon Manning on Mon, 8 Jan 2024 12:55:00 -0500)
> From: Simon Manning <simon@ecksd.com>
> Date: Mon, 8 Jan 2024 12:55:00 -0500
>
> For what it's worth, I've hit the same issue as Eason and have had to use the same workaround. The
> behavior is quite annoying with this (I think quite common?) setup because you can't really type
> without completion popups for simple words continuously showing up.
We add ispell-completion-at-point to completion-at-point-functions
with DEPTH of 10. So if other packages use DEPTH omitted or nil when
adding their functions to completion-at-point-functions, they should
be called before ispell-completion-at-point. Does that happen? if
not, why not? If it does happen, why isn't that a good enough
resolution of the situation where several candidates compete for the
privilege of providing a completion?
I took a liberty to add back Eason to the discussion, in the hope that
he could explain why DEPTH of 10 didn't solve his situation.
Thanks.
next prev parent reply other threads:[~2024-01-09 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2jzq0j1f4.fsf@foxmail.com>
2024-01-08 17:55 ` bug#67527: 30.0.50; FR: Add an option to disable ispell completion in text-mode Simon Manning
2024-01-09 13:33 ` Eli Zaretskii [this message]
2024-01-12 12:46 ` Eason Huang
2024-01-12 14:09 ` Eli Zaretskii
2024-01-13 9:03 ` Eason Huang
2024-01-20 9:19 ` Eli Zaretskii
2024-01-20 9:46 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-20 10:28 ` Eli Zaretskii
2024-01-20 10:33 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-20 10:56 ` Eli Zaretskii
2024-01-20 11:33 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-27 9:56 ` Eli Zaretskii
2023-11-29 10:31 Eason Huang
2023-11-29 13:18 ` Eli Zaretskii
2023-11-29 13:45 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-29 14:03 ` Eason Huang
2023-11-29 14:32 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-30 7:46 ` Eason Huang
2023-11-30 9:01 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 8:37 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 9:34 ` Daniel Mendler
2023-12-16 12:23 ` Dmitry Gutov
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=83jzoipr5v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67527@debbugs.gnu.org \
--cc=aqua0210@foxmail.com \
--cc=simon@ecksd.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 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).