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
I've been using flyspell-correct-wrapper as my main spell-checking interface for some time, and though I like it very much, the way it uses up to three universal-arguments, with two different behavior dimensions at play (repetition and direction) does put some cognitive load into calling it. And I admit I end up usually refraining from calling it with arguments for this reason.
Since the inclusion of the ability to skip a word on demand, independently of having called flyspell-correct-wrapper with an argument (in #58 (comment)), the rapid-mode became much less important to me. When I want do do a longer spell-checking session, I go to the hydra #69 instead.
So I came up with a simpler flyspell-correct-wrapper, which takes up only one argument, and changes the direction with the argument. I'm using it in the form:
(defunflyspell-correct-once-wrapper (&optionalarg)
"Correct spelling error once in a dwim fashion.One \\[universal-argument] changes direction of spelling errors search."
(interactive"P")
(when (or (not (markt))
(/= (markt) (point)))
(push-mark (point) t))
(flyspell-correct-move (point) arg))
which is, of course, just a simplified version of the current wrapper, and it does not enable rapid-mode.
A single binding, up to a single argument. And it solves 95% of my relevant cases, and for the other 5% I can fall-back to a more general command. The point, of course, is to reduce friction in the most common use case.
I'm still in the phase of "getting used to it", but I like it. And I thought it might also interest other users of flyspell-correct.
The text was updated successfully, but these errors were encountered:
the way it uses up to three universal-arguments, with two different behavior dimensions at play (repetition and direction) does put some cognitive load into calling it
Can't agree more! To be honest, the only times I use arguments - when I want to start rapid mode. Directions? I don't remember how it works.
hydra
I understand.
So I came up with a simpler flyspell-correct-wrapper, which takes up only one argument, and changes the direction with the argument. I'm using it in the form:
Can't agree more! To be honest, the only times I use arguments - when I want to start rapid mode. Directions? I don't remember how it works.
:-D
Well, thinking of it, this little function of mine is really just useful for those with the skip binding of #58 . I'm afraid I might be the only one. So I'll close this and leave this here "for the record" and for the reference of the more curious. ;-)
I've been using
flyspell-correct-wrapper
as my main spell-checking interface for some time, and though I like it very much, the way it uses up to three universal-arguments, with two different behavior dimensions at play (repetition and direction) does put some cognitive load into calling it. And I admit I end up usually refraining from calling it with arguments for this reason.Since the inclusion of the ability to skip a word on demand, independently of having called
flyspell-correct-wrapper
with an argument (in #58 (comment)), therapid-mode
became much less important to me. When I want do do a longer spell-checking session, I go to the hydra #69 instead.So I came up with a simpler
flyspell-correct-wrapper
, which takes up only one argument, and changes the direction with the argument. I'm using it in the form:which is, of course, just a simplified version of the current
wrapper
, and it does not enablerapid-mode
.A single binding, up to a single argument. And it solves 95% of my relevant cases, and for the other 5% I can fall-back to a more general command. The point, of course, is to reduce friction in the most common use case.
I'm still in the phase of "getting used to it", but I like it. And I thought it might also interest other users of
flyspell-correct
.The text was updated successfully, but these errors were encountered: