Re: Word completion in text modes

[Eshel Yaron]

Hi,

Eli Zaretskii <eliz@gnu.org> writes:

>> Text mode no longer binds `C-M-i` to anything, relying on the global
>> binding instead.  So there doesn't seem to be any reason to mention this
>> binding here anymore, just like it's not mentioned in the description of
>> `prog-mode` that follows this paragraph.  Does that make sense?
>
> But the global binding has a text-mode-special effect in Text mode,
> does it not?

Yes,

> Then we should change the text to mention that special effect, instead
> of removing it completely.  That's assuming the completion feature is
> still important enough to mention it in the manual.

Alright, I've added a few words about that in an updated, attached below.

>> > Did you check what happens when Flyspell mode is turned on in a buffer
>> > under Text mode or one of its descendants?
>>
>> Yes.  Unless one sets `flyspell-use-meta-tab` to nil, Flyspell mode binds
>> `C-M-i` to a completely different command, `flyspell-auto-correct-word`.
>
> And if flyspell-use-meta-tab is nil, what happens then under Flyspell
> mode?

Well, then Flyspell leaves `C-M-i` intact, and if you press those keys
you get whatever they are otherwise bound to.  Namely, with my patch, you
get `completion-at-point`, unless you've customized the new user option
to have Text mode bind `C-M-i` to `ispell-complete-word`, in which case
you get just that.

v3-0001-Unbind-C-M-i-in-Text-mode.patch
Description: Text Data