Re: Isn't flyspell-use-meta-tab default to nil more optimal?

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Richard Stallman]

    It seems a convention in emacs packages to use M-TAB to do symbol
    completion. While the default value of flyspell-use-meta-tab is t and
    that will override this key binding in various modes such as
    AUCTeX. Don't you think flyspell-use-meta-tab default to nil more
    optimal?

That would be an improvement in the very specific case you have
mentioned, but it would be inconvenient for all other uses of
Flyspell.  All in all, very much a change for the worse.

However, there might be a clever way that these two functionalities
could coexist on M-TAB.  If someone can figure out a spec that
would enable both functionalities to coexist, I am sure it could
be implemented.  The challenge is to design a good spec that
makes each functionality convenient when you want it.

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Lennart Borgman]

Richard Stallman wrote:
>     It seems a convention in emacs packages to use M-TAB to do symbol
>     completion. While the default value of flyspell-use-meta-tab is t and
>     that will override this key binding in various modes such as
>     AUCTeX. Don't you think flyspell-use-meta-tab default to nil more
>     optimal?
> 
> That would be an improvement in the very specific case you have
> mentioned, but it would be inconvenient for all other uses of
> Flyspell.  All in all, very much a change for the worse.
> 
> However, there might be a clever way that these two functionalities
> could coexist on M-TAB.  If someone can figure out a spec that
> would enable both functionalities to coexist, I am sure it could
> be implemented.  The challenge is to design a good spec that
> makes each functionality convenient when you want it.


Why not check if the major mode uses M-TAB?

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Richard Stallman]

    > However, there might be a clever way that these two functionalities
    > could coexist on M-TAB.  If someone can figure out a spec that
    > would enable both functionalities to coexist, I am sure it could
    > be implemented.  The challenge is to design a good spec that
    > makes each functionality convenient when you want it.


    Why not check if the major mode uses M-TAB?

That could be the first step, but then what?

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Kim F. Storm]

Richard Stallman <rms@gnu.org> writes:

>     > However, there might be a clever way that these two functionalities
>     > could coexist on M-TAB.  If someone can figure out a spec that
>     > would enable both functionalities to coexist, I am sure it could
>     > be implemented.  The challenge is to design a good spec that
>     > makes each functionality convenient when you want it.
>
>
>     Why not check if the major mode uses M-TAB?
>
> That could be the first step, but then what?

M-TAB often is useless anyway as it is taken by the window manager,
so making a lot of efforts to make other functions use it, doesn't
seem worth it to me.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[David Kastrup]

storm@cua.dk (Kim F. Storm) writes:

> Richard Stallman <rms@gnu.org> writes:
>
>>     > However, there might be a clever way that these two functionalities
>>     > could coexist on M-TAB.  If someone can figure out a spec that
>>     > would enable both functionalities to coexist, I am sure it could
>>     > be implemented.  The challenge is to design a good spec that
>>     > makes each functionality convenient when you want it.
>>
>>
>>     Why not check if the major mode uses M-TAB?
>>
>> That could be the first step, but then what?
>
> M-TAB often is useless anyway as it is taken by the window manager,

Not by all window managers, and besides, Esc TAB isn't, and I actually
use that not infrequently.

> so making a lot of efforts to make other functions use it, doesn't
> seem worth it to me.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Romain Francoise]

David Kastrup <dak@gnu.org> writes:

> Not by all window managers, and besides, Esc TAB isn't, and I actually
> use that not infrequently.

C-M-i is much easier to type.

-- 
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Leo]

On FRI, 8 DEC 2006, Romain Francoise wrote:

> David Kastrup <dak@gnu.org> writes:
>
>> Not by all window managers, and besides, Esc TAB isn't, and I actually
>> use that not infrequently.
>
> C-M-i is much easier to type.

Easier than C-.?

-- 
Leo

Re: Isn't flyspell-use-meta-tab default to nil more optimal?

[Leo]

On WED, 6 DEC 2006, Richard Stallman wrote:

>     It seems a convention in emacs packages to use M-TAB to do symbol
>     completion. While the default value of flyspell-use-meta-tab is t and
>     that will override this key binding in various modes such as
>     AUCTeX. Don't you think flyspell-use-meta-tab default to nil more
>     optimal?
>
> That would be an improvement in the very specific case you have
> mentioned, but it would be inconvenient for all other uses of
> Flyspell.  All in all, very much a change for the worse.

It seems not that bad since `C-.' is also bound to
flyspell-auto-correct-word.

,----[ C-h k C-. ]
| C-. runs the command flyspell-auto-correct-word
|   which is an interactive compiled Lisp function in `flyspell.el'.
| It is bound to C-..
| (flyspell-auto-correct-word)
| 
| Correct the current word.  This command proposes various successive
| corrections for the current word.
`----

regards,
-- 
Leo