Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

statistics not displayed #5

Open
heikkil opened this issue Jan 19, 2015 · 4 comments
Open

statistics not displayed #5

heikkil opened this issue Jan 19, 2015 · 4 comments

Comments

@heikkil
Copy link

heikkil commented Jan 19, 2015

The statistics is not shown when finishing the typing task when using speed-type-text. In contrast, speed-type-region works without problems. There might be something wrong in the way end of text is detected in the latter.

@hagleitn
Copy link
Owner

I can't reproduce issue issue. I've tried it many times, the stats always show up for me when I am done typing the text (in all modes). Can you give me more info? Does it always happen for you, only with certain pieces of text?

@heikkil
Copy link
Author

heikkil commented Jan 20, 2015

So far it has happened to me every time with function speed-type-text. I'll see later if I can use variables internal to your code to understand better what is going on.

@heikkil
Copy link
Author

heikkil commented Jan 21, 2015

I upgraded to latest version. Now the problem only appears occasionally.

I can not pinpoint any one action that causes that but it has something to do with counting the corrections and typed characters.

In one case I got to the end of the text and no matter what I did, moved the cursor, corrected mistakes, the variable speed-type--remaining had value 2. The stats were not displayed.

In an other occasion I had 10 lines of Iliad. I pressed space through the text and the cursor stopped 16 characters before the end and the stats were displayed. The fact that all Iliad lines had two spaces in the beginning of the line might have something to do with that.

Hopefully this helps.

@hagleitn
Copy link
Owner

Thanks - definitely appreciate the feedback. I'm glad the problem doesn't happen as often anymore, although I'm not sure I fixed anything in particular for this.

Let me walk through the code and see what could cause that. Both cases might be related to white spaces and how they are handled. I think the second one (hitting space through the text) is a good test case, I can try to repro this too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants