Opened 21 years ago

Closed 21 years ago

Last modified 15 years ago

#851 closed defect (fixed)

spell error messages are not passed on to the user in some cases

Reported by: walter.van.holst@… 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 levon, 21 years ago

Keywords: ui added

comment:2 by levon, 21 years ago

Cc: mmh@… added

comment:3 by levon, 21 years ago

* #883 has been marked as a duplicate of this bug. *

comment:4 by mmh@…, 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 levon, 21 years ago

Summary: ispell error messages are not passed on to the user properlyspell 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 levon, 21 years ago

Keywords: patch added
Owner: changed from jug to levon
qa_contact: levon@movementarian.orgleeming@lyx.org

I've fixed this as much as is possible.

comment:7 by levon, 21 years ago

Status: newassigned

comment:8 by levon, 21 years ago

Keywords: fixedintrunk added

comment:9 by Jean-Marc Lasgouttes, 21 years ago

So now that I applied your patch to 1.3.2cvs, is the bug fixed?

comment:10 by levon, 21 years ago

Resolution: fixed
Status: assignedclosed

fixed in cvs

comment:11 by levon, 21 years ago

Keywords: VERIFIED added

comment:12 by ps@…, 15 years ago

Keywords: fixedintrunk removed
Note: See TracTickets for help on using tickets.