budlabs / typiskt Goto Github PK

Hi, thinking about the Freedesktop XDG specifications, I think it would be easier to set typiskt's cache dir at $XDG_CACHE_HOME/typiskt, and have that default to ~/.cache/typiskt if XDG_CACHE_HOME is unset, so that you don't need to have the cache-dir option nor TYPISKT_CACHE variable, since the user can control the cache folder through the aforementioned XDG variable. I think it's more elegant this way

Hi, I don't know if this feature is desirable for you, but sometimes I just write a word entirely wrong and I would like to be able to delete it completely using the standard shell
keybinding ctrl+w(^w) to delete the word. This would make the program even more bash-like

Let me know what you think about it!

Similar to --width, it would be helpful to have --lines or --height to get a bit more preview that way.

Feature request.

Visual indicator that displays the fingers that should be used. Indicator can be toggled.

  '
||||     ||||
|  |/   \|  |
`           `

It would be great to see which words/letters were a cause for typos.

As an alternative (or an additional feature request), it would be great to see these stats over time, or to pass a flag to print them to stdout after you're done (or to a file). I'd like to see if I improve over time, if I have bad days, etc.

this was first reported in #7

When adding exercises with the add-gtypist-exercises.sh script the exercises from C seems to have the wrong order.

cheating is only checked for when you try to see the "next" exercise, i.e. pressing right/down.
but it is possible to navigate to any exercise simply by navigating backwards.

if you are on exercise 2/49, and press left 3 times you will be on 48/49.

Not sure if i want to fix this.

I'm very used to pressing Ctrl+h to delete a character backwards. My mind boggles when I realize that I need to press Backspace instead of Ctrl+h. Would you mind adding support to Ctrl+h? Thanks.

Hello!
printf complains about invalid numbers when displaying scores. This issue is specific to France, because the separator for floating point numbers is comma instead of dot. Adding LC_ALL=C at the beginning of lines 307, 629 and 630 seems to fix the issue for me.

Best regards.

cheating is only checked for when you try to see the "next" exercise, i.e. pressing right/down.
but it is possible to navigate to any exercise simply by navigating backwards.

if you are on exercise 2/49, and press left 3 times you will be on 48/49.

Not sure if i want to fix this.

Hi, thank you for this, finally an elegant and lightweight typing program that isn't gtypist(although add-gtypist-exercises.sh is very appreciated)!

I think it would be cool to have the possibility to customize colors; i.e. substitute the three color codes for setstatus() with environmental variables, or even better entries in the config file that looks something like [FgNorm,FgCorrect,FgWrong]. If you want, I can try to PR this myself, however I'm just learning bash scripting so that might take a while.

Also, the "modes" table in the manual now covers all of the "DESCRIPTION" section; reading this, I suspect that you just forgot adding .TE after this line.

I got /usr/bin/typiskt: line 603: bc: command not found when finishing the test and got a whoppin' 0.00 WPM.

This is not required by anything else on my system so I wouldn't call this "have no dependencies".

Hi, I noticed that when running $0 in exercise mode, i.e. with the gtypist exercises, there is a nice way to switch between exercises with either Down/Up or also Left/Right arrow
keys.

However, while this does work sometimes, oftentimes it will print out the raw keycodes (only the part after the escape code, so for example ^[[B for the Down key [in my
terminal] but only [B gets printed). I will attach a gif demonstrating the above.
Specifically, I can only reproduce this for the Down and Right keys. Up and Left seem to be working fine.

Uhm now that I think about it more, it could be intentional so that one does not skip over exercises(?)

In any case I don't thin it should be that way, since I might want to go Up/Down through completed exercises...

Let me know what you think about this

EDIT: Yea okay so I think there is an intentional part as I thought, since the bug does not happen when only scrolling through completed exercises... :o