My aspell is broken

L_Carver · 09-01-2019, 09:08 AM

This is Not a script question.

Site veterans will understand why I began that way by taking note of my screenname.

A week and more ago, I'd noticed aspell was failing with the -c/-check flag. A reboot usually cured it. Not so this morning. The version is @(#) International Ispell Version 3.1.20 (but really Aspell 0.60.7)
(returned by -v flag just now).

Any suggestions, or is this just a bug in the version. (Yes, I used apt to install it.)

Carver

RandomTroll · 09-01-2019, 09:26 PM

Mine returns the same version message. I just tried

Code:

 aspell -c somerandomfile

- it worked. I can't believe a reboot would be necessary. How does it fail?

L_Carver · 11-10-2019, 06:01 PM

Quote:

Originally Posted by RandomTroll

Mine returns the same version message. I just tried

Code:

 aspell -c somerandomfile

- it worked. I can't believe a reboot would be necessary. How does it fail?

It returns a blank screen with the conventional green (I have my Konsole set to green-on-black), which I can escape to stdin via Control-C. The word and possible alternate spellings are not displayed. Suggestions?

Carver

RandomTroll · 11-11-2019, 08:56 PM

Quote:

Originally Posted by L_Carver

It returns a blank screen with the conventional green (I have my Konsole set to green-on-black), which I can escape to stdin via Control-C. The word and possible alternate spellings are not displayed.

I don't understand this description. It's a console app. I run it at the command line. If it finds nothing wrong with a file it returns nothing. This may be a blank screen in Konsole, which I don't know.

scasey · 11-11-2019, 09:58 PM

Could it be outputting black text? Just a thought.

L_Carver · 01-23-2020, 12:57 PM

Quote:

Originally Posted by scasey

Could it be outputting black text? Just a thought.

That's exactly what it's doing. It's not even showing the lines with suspected misspellings. And I know the text files I'm directing it towards do have them.

Carver