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

Count issues with key sequences — Possible race condition for slow-to-run commands #39

Open
haberdashPI opened this issue Oct 9, 2024 · 1 comment

Comments

@haberdashPI
Copy link
Owner

Typing 1 space t doesn't pass the 1 count to the command t should run... 🤔 weird I haven't caught this before (do all other count commands I've used have a single key??)

@haberdashPI
Copy link
Owner Author

haberdashPI commented Oct 18, 2024

Mm... now I can't reproduced this problem. I think this is an issue with the specific extension the command was activating...

My working theory is that there is a race condition when VSCode is running quite slow that prevents the count from working in this edge case. But I haven't figured out how to recreate those conditions in a test that leads to the same bug yet.

@haberdashPI haberdashPI changed the title Count issues with key sequences Count issues with key sequences — Possible race condition for slow-to-run commands Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant