unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: "Jürgen Hartmann" <juergen_hartmann_@hotmail.com>
Cc: 20543@debbugs.gnu.org
Subject: bug#20543: 24.5; <SPC> in ispell-buffer accepts spelling for the whole line
Date: Fri, 08 Apr 2016 20:02:57 +0200	[thread overview]
Message-ID: <87fuuwvuzy.fsf@mbork.pl> (raw)
In-Reply-To: <DUB124-W164F44F8556B5F2FC09049A8DC0@phx.gbl> ("Jürgen Hartmann"'s message of "Sun, 10 May 2015 18:05:25 +0200")

On 2015-05-10, at 18:05, Jürgen Hartmann <juergen_hartmann_@hotmail.com> wrote:

> Using GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.2)--but
> this applies to former Emacs versions also--I found the following puzzling
> behavior of ispell-buffer:
>
> If a suspicious word is accepted once by pressing <SPC> in an interactive
> ispell-buffer session, all further occurrences of the same spelling on the
> same line are skipped, i.e. considered as accepted too.
>
> Here is an example:
>
> Open an Emacs 24.5 session (it is the same with Emacs 24.4) by
>
>    LC_ALL=C emacs -Q
>
> and enter the following line (with or without newline does not matter) in the
> *scratch* buffer:
>
>    The term charset is short for charset.
>
> Assume that the last word is a typo that should read "character set". Now
> change the dictionary to american and run ispell-buffer. The first occurrence
> of "charset" gets highlighted, but since it is correct here, we use <SPC> to
> accept it once and proceed. But oops... the spell-check finishes immediately
> without giving us the chance to correct the second occurrence of "charset" in
> that line.
>
> This finding was shortly discussed in help-gnu-emacs
> (http://lists.gnu.org/archive/html/help-gnu-emacs/2015-05/threads.html#00134)
> and it was Eli Zaretskii who indicated that there is the following comment in
> line 3651 of emacs-24.5/lisp/textmodes/ispell.el:
>
>    ;; Do not recheck accepted word on this line.
>
> This suggests that there might be a reason for that behavior. If this is
> true, what is it?

I've just seen this report.  I'm also very curious about that reason.

> Apart from that, I can not imagine why such a behavior might be desirable.
>
> Juergen


-- 
Marcin





  reply	other threads:[~2016-04-08 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 16:05 bug#20543: 24.5; <SPC> in ispell-buffer accepts spelling for the whole line Jürgen Hartmann
2016-04-08 18:02 ` Marcin Borkowski [this message]
2021-05-28  0:10   ` Lars Ingebrigtsen
2021-05-28  6:25     ` Eli Zaretskii
2021-05-29  2:08       ` Lars Ingebrigtsen

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=87fuuwvuzy.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=20543@debbugs.gnu.org \
    --cc=juergen_hartmann_@hotmail.com \
    /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).