bug#50776: add "ispell show where we looked" command

bug#50776: add "ispell show where we looked" command

[積丹尼 Dan Jacobson]

Regarding

     ispell-help is an autoloaded compiled Lisp function in ‘ispell.el’.

     (ispell-help)

     Display a list of the options available when a misspelling is encountered.

     Selections are:

     DIGIT: Replace the word with a digit offered in the *Choices* buffer.
     SPC:   Accept word this time.
     ‘i’:   Accept word and insert into private dictionary.
     ‘a’:   Accept word for this session.
     ‘A’:   Accept word and place in ‘buffer-local dictionary’.
     ‘r’:   Replace word with typed-in value.  Rechecked.
     ‘R’:   Replace word with typed-in value.  Query-replaced in buffer.  Rechecked.
     ‘?’:   Show these commands.
     ‘x’:   Exit spelling buffer.  Move cursor to original point.
     ‘X’:   Exit spelling buffer.  Leaves cursor at the current point, and permits
             the aborted check to be completed later.
     ‘q’:   Quit spelling session (Kills ispell process).
     ‘l’:   Look up typed-in replacement in alternate dictionary.  Wildcards okay.
     ‘u’:   Like ‘i’, but the word is lower-cased first.
     ‘m’:   Place typed-in value in personal dictionary, then recheck current word.
     ‘C-l’:  Redraw screen.
     ‘C-r’:  Recursive edit.
     ‘C-z’:  Suspend Emacs or iconify frame.

Please add one more:
Show all the dictionaries that were checked when looking for (and not
finding) the word.

That way one could figure out why e.g., "jitter" is misspelled in emacs,
but not in the shell's ispell.

Sure, there are various alists, but we want to see where it really looked.

bug#50776: add "ispell show where we looked" command

[Eli Zaretskii]

> From: 積丹尼 Dan Jacobson
>  <jidanni@jidanni.org>
> Date: Fri, 24 Sep 2021 21:20:39 +0800
> 
> Please add one more:
> Show all the dictionaries that were checked when looking for (and not
> finding) the word.
> 
> That way one could figure out why e.g., "jitter" is misspelled in emacs,
> but not in the shell's ispell.
> 
> Sure, there are various alists, but we want to see where it really looked.

I don't understand: there's only one dictionary, the current one.

bug#50776: add "ispell show where we looked" command

[積丹尼 Dan Jacobson]

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> I don't understand: there's only one dictionary, the current one.

That's great to know.

So it the new key press should say:
Checked for "jitter" and didn't find it in
1. /usr/..../bla

That way we can be sure.

bug#50776: add "ispell show where we looked" command

[Eli Zaretskii]

> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: 50776@debbugs.gnu.org
> Date: Fri, 24 Sep 2021 21:54:47 +0800
> 
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> EZ> I don't understand: there's only one dictionary, the current one.
> 
> That's great to know.
> 
> So it the new key press should say:
> Checked for "jitter" and didn't find it in
> 1. /usr/..../bla
> 
> That way we can be sure.

You are saying that the user who turns on spell-checking has no idea
which dictionary (actually, which language) he/she is using?

bug#50776: add "ispell show where we looked" command

[積丹尼 Dan Jacobson]

EZ> You are saying that the user who turns on spell-checking has no idea
EZ> which dictionary (actually, which language) he/she is using?

Yup. An average system has tons of dictionaries and tons of spelling
commands (within and without emacs,) so without an "strace" it is hard
to know which is using which.

bug#50776: add "ispell show where we looked" command

[Juri Linkov]

> So it the new key press should say:
> Checked for "jitter" and didn't find it in
> 1. /usr/..../bla

`ispell-region' displays such message:

  Spell-checking region using hunspell with klingon dictionary...

So `?' for `ispell-word' could do the same.

bug#50776: add "ispell show where we looked" command

[Eli Zaretskii]

> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: 50776@debbugs.gnu.org
> Date: Fri, 24 Sep 2021 22:32:43 +0800
> 
> EZ> You are saying that the user who turns on spell-checking has no idea
> EZ> which dictionary (actually, which language) he/she is using?
> 
> Yup. An average system has tons of dictionaries and tons of spelling
> commands (within and without emacs,) so without an "strace" it is hard
> to know which is using which.

But then how do you know that spell-checking even makes sense?  If you
are spell-checking English text with a French or Japanese or Chinese
dictionary, why would you expect anything useful to come out of that?

bug#50776: add "ispell show where we looked" command

[積丹尼 Dan Jacobson]

Sort of like how C-u C-x = will show one the font used,
    x:-eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0 (#xBF6E)
So I would like a way to have it show the dictionary(s) used.

bug#50776: add "ispell show where we looked" command

[Lars Ingebrigtsen]

Juri Linkov <juri@linkov.net> writes:

> `ispell-region' displays such message:
>
>   Spell-checking region using hunspell with klingon dictionary...
>
> So `?' for `ispell-word' could do the same.

The three help lines it displays as already are pretty jam-packed...  I
don't see any obvious place to squeeze that information in without
making it a four-line help, and I'm not sure that would be helpful.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#50776: add "ispell show where we looked" command

[積丹尼 Dan Jacobson]

Anyway, user notices emacs says "jitter" is a misspelling.
There should be an easy way to report that it is not a misspelling,
so that others won't encounter the problem.
So maybe an ispell-report-non-problem-word function.

bug#50776: add "ispell show where we looked" command

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> The three help lines it displays as already are pretty jam-packed...  I
> don't see any obvious place to squeeze that information in without
> making it a four-line help, and I'm not sure that would be helpful.

So I think the conclusion here is that we don't want to add this
information, and I'm therefore closing this bug report.