NUSPELL(1)
β¨ NUSPELL(1) β User Commands π
π NAME π
nuspell β command-line tool for spellchecking. That's the whole gig, bestie: it checks your spelling and it's lowkey iconic.
This is from the User Commands manual, and your girl is about to walk you through every single flag, no cap. π«Ά
πΈ SYNOPSIS πΈ
Two moods, both valid:
nuspell [-d dict_NAME] [OPTION]... [FILE]...
nuspell -D|--help|--version
π¦ DESCRIPTION π¦
It checks the spelling of each FILE. If no FILE is specified, it checks standard input instead. The text in the input is first segmented into words with an algorithm that recognizes punctuation, and then each word is checked. Literally a little word bouncer: punctuation gets handled, words get checked, slay. β¨
π OPTIONS π
Okay so here's the menu. Every option, no skipping, periodt.
-d,--dictionary=di_CTβ Use thedi_CTdictionary. Only one is supported at a time. A dictionary consists of two files with extensions.dicand.aff. The-doption accepts either the dictionary name without filename extension, usually a language tag, or a path (with slash) to the.afffile including the filename extension. When just a name is given, it will be searched among the list of dictionaries in the default directories (see option-D). When a path to.affis given, only the dictionary under the path is considered. When-dis not present, the CLI tools tries to load a dictionary using the language tag from the active locale. Bestie, it's doing its best with your locale. π-D,--list-dictionariesβ Print search paths and available dictionaries and exit. Like a little dictionary tour. πΊοΈ--encoding=ENCβ Set both input and output encoding.--input-encoding=ENCβ Set input encoding, default isUTF-8.--output-encoding=ENCβ Set output encoding, default isUTF-8.--helpβ Print short help.--versionβ Print version number.
π EXIT STATUS π
Returns error if the argument syntax is invalid, if the dictionary can not be loaded, or if some input file can not be opened. Otherwise, spell checking has occurred and returns success. So if it exits happy, the words got checked, fr fr. β¨
π ENVIRONMENT π
Environment variables do be influencing things:
DICTIONARYβ Specify dictionary, same as option-d.DICPATHβ Path to additional directory to search for dictionaries.
π CAVEATS π
Listen bestie, this part matters. The CLI tool is primarily intended to be used interactively by a human. The input is plain text, and the output is mostly plain text with some symbols and words that are meant to be read by a human and not by a machine. The format of the output is not strictly defined and may change, thus it is not machine-readable. Other programs should use the C++ library directly, which has stable API.
Machine-readable? Not this. Human-readable? Absolutely, and kinda cute. But don't parse the output like it's a stable API, because it's not. π
π EXAMPLES π
Try these:
nuspell -d en_US file.txt
nuspell -d ../../subdir/di_CT.aff
π§ REPORTING BUGS π§
Found a bug? Don't suffer in silence, bestie. Bug reports: https://github.com/nuspell/nuspell/issues
π COPYRIGHT π
Copyright 2016-2026 Nuspell authors. Respect the icon. π
π₯ SEE ALSO π₯
- Full documentation: https://github.com/nuspell/nuspell/wiki
- Home page: http://nuspell.github.io/
π AUTHORS π
Dimitrij Mijoski.
Okay bye bestie β this was NUSPELL(1) from Nuspell 5.1.9, dated 2026-09-11. Mwah πβ¨
π¦ where this page comes from
- arch rolling: nuspell 5.1.9-1 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms