nstefan002 / speedtyper.nvim Goto Github PK

Currently the WPM is estimated as the number of characters typed divided by 5 as an average word length. This makes sense when typing words from a dictionary as they tend to be longer than the average word length. Also it nulls the variation of the WPM based on the specific words selected at the start of the game.

        wpm = (n_chars - n_mistakes) / 5 * (60 / time_sec)
        accuracy = (n_chars - n_mistakes) / n_keypresses * 100

On the other hand, when typing sentences, a more adequate calculation would be to take into account the actual content being typed.

It makes sense to keep both approaches and let the user choose as an option.

Also, currently correcting mistakes in typing isn't taken into account. There can be arguments for and against this but it makes sense to also take this into account.

At the end the WPM and Accuracy should be calculated like so:

        wpm = n_words * (60 / time_sec)
        accuracy = n_correct / n_words * 100

Description

Speedtyper window sometimes does not close when opening netrw inside of it

Steps to reproduce

1. :SpeedTyper
2. :Ex

Expected behavior

Speedtyper window should close.

Environment

• Neovim version: [0.9.5, Nightly]

When I double the window height from 5 to 10 the word list size in the Countdown game doesn't increase to fill the new window - it remains at the 5 row height.

It would be nice if the user input is paused for a bit, or even better completely disabled, after the game finishes and the stats are displayed.

Otherwise depending on what word your typing you can edit over the displayed text.

I tried the following:

1. Pause Neovim using vim.wait(500). This doesn't really work, if it does pause Vim the keypresses are still accumulated sent after the wait.

2. Turn off modifiable via api.nvim_buf_set_option(0, "modifiable", false), this I think is a good choice but can lead to a bunch of E21: Cannot make changes, 'modifiable' is off. I couldn't find if this can be suppressed at a buffer level..

3. Prompt user for input, e.g. "Press Enter to continue ..." but vim.fn.input() would open a new prompt. Maybe a custom function could be implemented 🤔

I'm pushing the 2. PR - seems the cleanest.

Ignore if it doesn't make sense 😅 :

This is especially visible for narrower windows:

As per the TODO writing sentences is an important option to have; it is faster than writing random words and is a more adequate measure of writing speed.

When the words are exhausted in the countdown game the buffer refreshes with new words but the WPM also resets.

Description

netrw text 'merges' with the current buffer text after closing the Speedtyper window in which the user tried to open netrw

Steps to reproduce

1. :SpeedTyper
2. :Ex (netrw is not the buffer 'behind' the Speedtyper window)

Expected behavior

Speedtyper window closes normally and netrw opens up in a normal way (or doesn't open up at all, but the first option makes more sense)

Environment

• Neovim version: [0.9.5, Nightly]

Describe the problem

Any plans on having a text for typing configurable? Or maybe turning it into real typing tutor?

Describe the solution

I decompiled (freed or stole if you will) lessons from Solo On Keyboard Dvorak Edition and I think we could use it. This is the intellectual property of russians, and they abandoned the blob moving to web version a while ago. Besides, hence they bomb city I live right now I don't see how complain from them merits a response.

The stopwatch.util.update_extmarks() doesn't trigger the eng_game(true). The game ends with end_game(false).

Awesome plugin 😎

After finishing the countdown game when I quit the results window with :q it closes with the following error:

"lua/plugins/speedtyper.lua" 46L, 1731B written
Error detected while processing BufLeave Autocommands for "*":
Error executing lua callback: ...dtyper.nvim/lua/speedtyper/game_modes/countdown/init.lua:48: handle 0x55b742f94050 is already closing
stack traceback:
	[C]: in function 'close'
	...dtyper.nvim/lua/speedtyper/game_modes/countdown/init.lua:48: in function 'stop'
	.../lazy/speedtyper.nvim/lua/speedtyper/game_modes/init.lua:37: in function 'end_game'
	.../lazy/speedtyper.nvim/lua/speedtyper/game_modes/init.lua:25: in function <.../lazy/speedtyper.nvim/lua/speedtyper/game_modes/init.lua:24>

And the cursor remains hidden in the original window.

• Neovim version: 0.9.4