help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ispell-buffer skips repetitive suspects after the first is accepted


From: Francis Belliveau
Subject: Re: ispell-buffer skips repetitive suspects after the first is accepted
Date: Thu, 7 May 2015 19:01:06 -0400

This is clearly an intended feature.  I am personally annoyed by the inability 
to indicate something suspicious is valid for a particular document.  I do not 
want such things added to my dictionary because they are likely not valid for 
other documents.

That said I can understand how this would not be liked by all.  If a bug report 
is filed, I would hope that it is solved by configuration choice, rather than 
just forcing everybody to accept it the other way.

That’s my opinion and I am sticking with it:-)

> On May 7, 2015, at 10:58 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Jürgen Hartmann <juergen_hartmann_@hotmail.com>
>> Date: Thu, 7 May 2015 10:14:21 +0200
>> 
>> If a suspicious word is accepted once by pressing <SPC> in an interactive
>> ispell-buffer session, all further occurrences of the same word on the same
>> line are skipped.
>> 
>> 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 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 an proceed. But oops... the spell-check finishes immediately
>> without giving us the chance to correct the second occurrence of "charset" in
>> that line.
>> 
>> Is this a bug or a difficult to understand feature.
> 
> Looks like a deliberate "feature": the comment there explicitly says:
> 
>              ;; Do not recheck accepted word on this line.
> 
> Can't say I understand why, so feel free to file a bug report.
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]