Re: [bug-gtypist] Typo in KTouch lessons for German

[Felix Natter]

hello Sebastian,

Sebastian Hoffmann <address@hidden> writes:
> I have been wondering why the interface was behaving weird in that
> instance /one character look-ahead; I haven't even noticed other such
> features). As I see it, there's two sensible approaches:
>
> * The point of gtypist is to drill the right keystrokes; do not allow
> incorrect input at all, except that it increases the count of
> errors. This has the advantage of the user always ends with the right
> stroke, which might improve muscle memory.  * The point of gtypist is
> to prepare for real-world environments. Allow for any input, do not
> help in any way that a text editor wouldn't, do allow for, or even
> require, backspace. I've never seen look-ahead correction in the wild.
>
> Either way, assisting functions make no sense to me. I haven't looked
> into them any further, though, as the point of gtypist to me is to
> *not* become familiar with it, but just to transition from fast
> non-blind typing to slow but proper touch-typing; further practice
> will happen in actual editors.

So you agree that we shall disable all the 'smart' stuff by default,
but add an option to enable it on request?  If many users complain,
we could enable it by default again (but I wouldn't count on it).

Cheers and Best Regards,
Felix

> Beste Grüße, Sebastian Hoffmann
>
> On Sat, Mar 18, 2017 at 6:51 PM, Felix Natter <address@hidden> wrote:
>
>     hello Sebastian,
>    
>     Sebastian Hoffmann <address@hidden> writes:
>     > "völlig" is misspelled as "vökkig".
>    
>     Thanks for the fix, committed in branch-2.9 and master.
>    
>     > Patch was created by diffing the while as and where installed,
>     > and a fixed version in $HOME; is that the canonical way? Having
>     > different paths for the file looks weird to me.
>    
>     For such a simple patch (and even for complex patches), this is
>     fine :-)
>    
>     If you want to save yourself work, you could create a patch
>     against a git branch, but this requires that you build the code
>     yourself (unless you only change lessons, in which case you just
>     need to clone the git repo). With git, you just change the files,
>     and create a diff with: $ git diff > mypatch.diff
>    
>     What do you think about all the "word processor adjustments" (sync
>     ahead and such)? We are thinking about dropping all of these
>     functions, and requiring the user to type the text exactly, see:
>     https://lists.gnu.org/archive/html/bug-gtypist/2016-10/msg00004.html
>    
>     Cheers and Best Regards, -- Felix Natter
>

-- 
Felix Natter