#851 closed defect (fixed)
spell error messages are not passed on to the user in some cases
Reported by: | Owned by: | levon | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | spell | Version: | 1.3.0cvs |
Severity: | normal | Keywords: | ui patch VERIFIED |
Cc: | mmh@… |
Description
If you try to spell check a document in a language for which there is no ispell
dictionary installed LyX seems to freeze for a while and then gives an error
message stating that something went wrong with the spellchecker and that it has
been killed. Running LyX with the debug parameter reveals however that ispell
tells LyX that it can't find the proper hash file. LyX should tell that the user
IMO, this error is confusing.
Change History (12)
comment:1 by , 21 years ago
Keywords: | ui added |
---|
comment:2 by , 21 years ago
Cc: | added |
---|
comment:3 by , 21 years ago
comment:4 by , 21 years ago
The bug affects aspell as well and leads to silent data loss if the specified personal
dictionary file is not correct. The aspell warning is never shown (in the qt frontend).
Any words you seemingly add to that file are silently discarded!!
Please update the bug summary to reflect this, normal users are not allowed to update
titles, as I just learned, thank you.
comment:5 by , 21 years ago
Summary: | ispell error messages are not passed on to the user properly → spell error messages are not passed on to the user in some cases |
---|
We need to collect exactly which cases do not pass errors back. The
pspell backend has error reporting machinery at least, and some errors
do get reported back.
comment:6 by , 21 years ago
Keywords: | patch added |
---|---|
Owner: | changed from | to
qa_contact: | levon@movementarian.org → leeming@lyx.org |
I've fixed this as much as is possible.
comment:7 by , 21 years ago
Status: | new → assigned |
---|
comment:8 by , 21 years ago
Keywords: | fixedintrunk added |
---|
comment:11 by , 21 years ago
Keywords: | VERIFIED added |
---|
comment:12 by , 15 years ago
Keywords: | fixedintrunk removed |
---|
* #883 has been marked as a duplicate of this bug. *