Add a New Comment Rich Markup
Currently, gtypist tries to be clever in detecting typing errors. This behaviour is sometimes undesirable and, at the least, we should provide a command-line option to disable it. For example, if a typing lesson consists of: abcd and you type "bcd" instead, accidentally missing out the "a", then gtypist correctly shows that there was only one error: abcd ^bcd It achieves this by accepting the character after the current character (if it matches) and marking the current character as an error. But it goes further. Suppose you were to type "bbcd". Again, there is only one error here (the first "b" instead of the "a"). In this scenario, gtypist detects that the subsequent "b" is not a subsequent error and ignores it altogether. While very clever, it would be nice to be able to disable this detection via command line option.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.12