Closed tpadioleau closed 4 years ago
Hey @tpadioleau
Thank you very much for your feedback and for time you spent digging into it! In my own configurations I am also split flyspell-correct
and flyspell-correct-<interface>
configurations, because it makes sense to.
I would gladly accept PR improving documentation.
Fixed via #76
Hi,
I tried to use
flyspell-correct-helm
flavor using the setup you proposeIt doesn't seem to work for me. The key binding is not set, it is actually still bound to
flyspell-auto-correct-previous-word
. Moreover if I use manually theflyspell-correct-wrapper
function, it complains sayinghelm-M-x-execute-command: Symbol’s function definition is void: flyspell-correct-helm
.The simpler setup you suggest
is working for me (key binding and it uses helm version). But I notice that it doesn't seem to do operations in the same order as in the use-package setup.
I think there are two problems with the use-package setup:
flyspell-mode-map
, a first fix could beit makes it closer to the simple setup you suggest.
flyspell-correct-wrapper
is not part offlyspell-correct-helm
? A workaround could be to split into two distinct use-package declarations(use-package flyspell-correct-helm :after flyspell-correct)