You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally I need spell-checking without flyspell-mode. In that case I would use ispell-word. However, I really like the interface of this package and want to use it as a replacement of ispell-word.
I wonder if it is a reasonable goal of this project to provide and maintain some commands that work without flyspell-mode?
Thanks!
PS: Currently flyspell-correct-at-point mostly works without flyspell-mode. However, we need to initialize the spell-checker properly:
diff --git a/flyspell-correct.el b/flyspell-correct.el
index c661340..2992d89 100644
--- a/flyspell-correct.el+++ b/flyspell-correct.el@@ -224,6 +224,7 @@ Adapted from `flyspell-correct-word-before-point'."
(unless flyspell-correct-interface
(error "Could not correct word because `flyspell-correct-interface' is not set"))
(let ((res))
+ (ispell-set-spellchecker-params)
;; use the correct dictionary
(flyspell-accept-buffer-local-defs)
(flyspell-correct--highlight-add)
Besides, flyspell-correct-highlight does not work.
Other public commands probably do not work because they need the overlays of flyspell-mode.
The text was updated successfully, but these errors were encountered:
Hi!
Thanks for this package! I really enjoy it.
Occasionally I need spell-checking without
flyspell-mode
. In that case I would useispell-word
. However, I really like the interface of this package and want to use it as a replacement ofispell-word
.I wonder if it is a reasonable goal of this project to provide and maintain some commands that work without
flyspell-mode
?Thanks!
PS: Currently
flyspell-correct-at-point
mostly works withoutflyspell-mode
. However, we need to initialize the spell-checker properly:Besides,
flyspell-correct-highlight
does not work.Other public commands probably do not work because they need the overlays of
flyspell-mode
.The text was updated successfully, but these errors were encountered: