Typing in the find input box during recording can cause unexpected cursor movement on the playback

[tshino]

ref. #31 (comment)

Overview
Typing in the find input box during recording may cause unexpected cursor movements during playback.

Details
As stated in the README, this extension has a limitation that typing in the find input box is not recorded due to the lack of capabilities of VS Code API to capture them.
For example, when you type a word like 'foo' in the find input box during recording, nothing should be recorded.
But at the same time, the cursor may move to somewhere in the document, which indicates the word matches the text at the location.
This cursor movement causes the problem.

Workaround
Type the word in the find input box BEFORE starting recording, and record only the find trigger ('f3') and edits you want to do.

[GreenAsJade]

Man, if only this could be dealt with, this wonderful feature would be complete.

Thanks for the workaround in the mean time.

[tshino]

Thank you for the comment.
I'm still investigating this issue and trying to find a way to solve it.

[tshino]

At last, I've fixed this issue. 😊
The next release will soon be published.