So I saw this, fought with my package manager (cue Karen joke fighting with the manager) to get it installed, first test fails.

So if it's not obvious I'm 12 (at hart <-- see what I did there?) I tested the with the word "fert." The expectation was the top match should be fart but fart is no where to be seen...or smelt...(again see what I did there? I've got a million of them I tellz ya!) Swing and a miss. Then I tried "hart", again expecting heart, swing and a miss. If it wasn't obvious "smelt" also failed to suggest smelled.

Is there a way to improve matching? So far it's failed every test word but one.

for example:

❯ dym tomrrow
Did you mean?
1. tomorrow
2. borrow
3. morrow
4. orrow
5. sorrow

I want it to be like

❯ dym tomrrow -y
Did you mean?
1. tomorrow
2. borrow
3. morrow
4. orrow
5. sorrow

Which word should be copied: 1
"tomorrow" has been copied to your clipboard.

-y flag stands for yanking the text to clipboard

This PR fixes the following warning which is shown during cargo build:

warning: found module declaration for lib.rs
 --> src/main.rs:3:1
  |
3 | pub mod lib;
  | ^^^^^^^^^^^^
  |
  = note: lib.rs is the root of this crate's library target
  = help: to refer to it from other targets, use the library's name as the path
  = note: `#[warn(special_module_name)]` on by default

warning: `didyoumean` (bin "dym") generated 1 warning

I would really appreciate a different exit code when my input word is spelled correctly vs when it is not.

Additionally, I would like to see a different message noting that my input was spelled correctly. Sometimes (when I forget to specify -v), I have to take a moment to double check if the first result is different from my input word.

$ dym supercalifragilisticexpialidocious # correct spelling
supercalifragilisticexpialidocious is spelled correctly
$ echo $?
0

$ dym supercalifragilisticexpialidociouX # last char typo
Did you mean?
1. supercalifragilisticexpialidocious
2. supercalifragilistic
3. superphlogistication
4. superartificiality
5. supercapabilities
$ echo $?
1

Regardless, thanks for your work on dym. It is very helpful as is!

Some language files have encoding problems. I'm aware of the problem affecting Russian, Bosnian and possibly Estonian.

I can probably have a closer look at some others in the coming week.

Improves performance

Example

Before:

time ./target/release/dym phoanix -n 10000 > test

real    0m1.459s
user    0m1.432s
sys     0m0.020s

After:

time ./target/release/dym phoanix -n 10000 > test

real    0m0.498s
user    0m0.485s
sys     0m0.010s

On Windows, Powershell handles ANSI escape codes incorrectly, but colored lets you fix that behavior. See https://github.com/mackwic/colored/issues/59

Before:

After:

Add man pages and shell completions via a build.rs build script. This PR also refactors the clap Cli struct into its own file to improve modularity.

closes #8 closes #9

Use wordlists external to the binary to provide support for the following languages:

• Afrikaans
• Arabic
• Azerbaijani
• Belarusian
• Bulgarian
• Breton
• Bosnian
• Catalan
• Czech
• Welsh
• Danish
• German
• Greek
• English
• Spanish
• Estonian
• Basque
• Faeroese
• French
• Frisian
• Galician
• Hungarian
• Indonesian
• Icelandic
• Italian
• Kazach
• Korean
• Latin
• Luxembourgish
• Lithuanian
• Latvian
• Malaysian
• Norwegian
• Dutch
• Norwegian
• Occitan
• Polish
• Romanian
• Russian
• Slovak
• Slovenian
• Albanian
• Serbian
• Sesotho
• Swedish
• Swahili
• Tajik
• Turkmen
• Tagalog
• Tswana
• Turkish
• Tsonga
• Tatar
• Ukranian
• Venda
• Vietnamese
• Xhosa
• Yiddish
• Zulu

A list of supported languages can be obtained using the --print-langs flag, and the language files can be updated by using the --update-langs flag. You can select the desired language by passing the -l or --lang flag followed by the two letter language code (also provided in --print-langs)

Add the ability to read the search_term argument from standard input if no argument is provided. Standard input will be ignored if there is a search_term argument provided. An error message will be printed if neither standard input or a search_term argument are provided.

Add support for copying to the system clipboard. This was harder than expected as you need a workaround for X11/Wayland. X11 and Wayland clear the clipboard when the process that sets it exits, so dym will now fork and keep a process around to maintain the clipboard until the value stored in the clipboard changes, at which point the child process will exit.

resolves #1

As the title says (with an optional flag), show the differences between the queried and resulting words. Showing removals is not recommended as that would require some sort of thinner character which I don't think would look very nice. Showing additions and substitutions should be easy enough. Showing transpositions as two insertions may be simpler? I'm not quite sure how that would work, but it should be doable.

As the title describes, the child process created to keep the clipboard from being cleared on X11/Wayland does not terminate when the clipboard changes on sway. On Hyprland (still in early development), it terminates right away. Not that sway is using wlroots and Hyprland is using wlroots-git. This is likely an issue with the clipboard being read and thus is likely not within the scope of this project, but instead in the cli-clipboard dependency.