From: Juri Linkov <juri@linkov.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: 50443@debbugs.gnu.org, roni kallio <roni@kallio.app>
Subject: bug#50443: Fwd: Flyspell error traversal additions
Date: Thu, 09 Sep 2021 20:24:44 +0300 [thread overview]
Message-ID: <87mtolviln.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkm==pCKz+0eirFtmcZr-fKx5m7cOKZYPRt1KGCTX5Bc8BA@mail.gmail.com> (Stefan Kangas's message of "Tue, 7 Sep 2021 02:22:29 +0200")
> 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.
next prev parent reply other threads:[~2021-09-09 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sg6lchgc.fsf@kallio.app>
[not found] ` <87r1m5ch9n.fsf@kallio.app>
2021-09-07 0:22 ` bug#50443: Fwd: Flyspell error traversal additions Stefan Kangas
2021-09-07 5:57 ` Eli Zaretskii
2021-09-09 20:58 ` Roni Kallio
2021-09-19 16:05 ` Stefan Kangas
2021-12-27 3:12 ` Stefan Kangas
2022-03-24 9:06 ` Lars Ingebrigtsen
2022-08-25 14:20 ` Lars Ingebrigtsen
2021-09-09 17:24 ` Juri Linkov [this message]
2021-09-10 6:39 ` Juri Linkov
2021-09-10 6:49 ` Stefan Kangas
2021-09-10 16:12 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtolviln.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=50443@debbugs.gnu.org \
--cc=roni@kallio.app \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).