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 the di_CT dictionary. Only one is supported at a time. A dictionary consists of two files with extensions .dic and .aff. The -d option accepts either the dictionary name without filename extension, usually a language tag, or a path (with slash) to the .aff file 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 .aff is given, only the dictionary under the path is considered. When -d is 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 is UTF-8.
  • --output-encoding=ENC β€” Set output encoding, default is UTF-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 2016-2026 Nuspell authors. Respect the icon. πŸ’œ


πŸ”₯ SEE ALSO πŸ”₯


πŸ’œ 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