emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org, Sharon Kimble <boudiccas@skimble.plus.com>
Subject: Re: How to jump from one spelling mistake to the next?
Date: Fri, 19 Mar 2021 23:55:08 -0400	[thread overview]
Message-ID: <87r1ka4gyr.fsf@kyleam.com> (raw)
In-Reply-To: <CAJcAo8vp9bh2-M7arhe5d8=s77kJCE4asyquhDsn_uxZjuAcFA@mail.gmail.com>

Samuel Wales writes:

> i wonder why the generic next-error is not used.

Hmm, good question.  Ignoring any historical reasons for why flyspell
does what it does, a quick search on the Emacs lists makes me think at
least one open issue is how to prioritize/combine different next-error

 * https://lists.gnu.org/archive/html/emacs-devel/2018-04/msg00207.html

 * https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30674#8

That's getting a bit off-topic for the Org mode list though...

  reply	other threads:[~2021-03-20  3:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  2:00 Sharon Kimble
2021-03-20  2:37 ` Timothy
2021-03-20  2:44 ` Kyle Meyer
2021-03-20  3:08   ` Samuel Wales
2021-03-20  3:55     ` Kyle Meyer [this message]
2021-03-20 12:29   ` Dr. Arne Babenhauserheide
2021-03-20 12:33     ` Joost Kremers

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1ka4gyr.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=boudiccas@skimble.plus.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    --subject='Re: How to jump from one spelling mistake to the next?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).