[Feature request]: change colors and minor Manual issue #7
Labels
No labels
bug
dependency
documentation
duplicate
enhancement
fixed
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
bud/typiskt#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, thank you for this, finally an elegant and lightweight typing program that isn't gtypist(although
add-gtypist-exercises.shis 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
.TEafter this line.About the
gtpyist-exercisesscript, I noticed comparing with the original exercises that the numbering of some sets of exercises is not correct.For instance, C-series' first lesson is consistently downloaded to file C/4 instead of C/1, which is what I assume to be the intended behavior. Instead, C/0 and C/1 are actually the first two parts of lesson C10 (and now that I wrote this down I think the issue might have something to do with single-digit numbering since it's C
10; although I have not understood theawksection of the script quite yet)Hello Bacho! Thanks for input. Changing colors in the settings would be a great addition, i will look into how it could be setup, but i think it will be customizable to the extent one can set the color number (0-7) for the colors. Using names or hexadecimal values (#FFF000 etc) have limited cross terminal support.
I will see what's up with the manpage, i use md2man to automatically generate the manpage from markdown, looks like i need to add one more linebreak after the table.
For some reason, the C-series is named in a completely different manner then the other exercises. so i just autonumbered them, i think i can fix it so we get the correct order.
Also, I should mention, that i do development on the 'dev' branch, which you will see have a different filestructure and stuff, and it uses bashbud which is my own crazy templating thing.
Im testing out color options now, feels great, also makes the code more readable. I will add this to the config file (only place to change the colors)
the values can be used in the script with the global variables
_statuscorrect_statuserror_statusactive. Making it easier to understand then random 1, 2 and 3 which was the case prior.regarding the manpage it seems to be a bug in go-md2man , i made a pullrequest to them, and guess i will use my fork of it till it gets fixed. https://github.com/cpuguy83/go-md2man/issues/59
reopened as a reminder to look into the gtypist C exercises.