GNU bug report logs -
#50443
Fwd: Flyspell error traversal additions
Previous Next
Reported by: Stefan Kangas <stefan <at> marxist.se>
Date: Tue, 7 Sep 2021 00:23:02 UTC
Severity: wishlist
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #11 received at 50443 <at> debbugs.gnu.org (full text, mbox):
> IMO the best course of action would be to modify
> `flyspell-goto-next-error' to accept a prefix argument. The prefix
> would control the direction and number of jumps performed; negative
> arguments would jump backwards -ARG errors (by calling
> flyspell-goto-previous-error), while positive arguments would jump
> forwards ARG errors. This would be similar to how commands like
> `forward-word' handle prefix arguments. This would allow us to leave
> the mode-map unchanged, but still distribute the improvement to all
> users.
Adding a negative argument to `flyspell-goto-next-error'
is the most non-conflicting solution. There was an idea
to use 'M-g n' and 'M-g p' to navigate flyspell errors.
But I don't believe this is workable since often 'M-g n'
and 'M-g p' are needed to navigate errors or search hits
displayed in another window with a list of results.
This bug report was last modified 2 years and 269 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.