macOS: Added workaround for entering text that starts with newline #261
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pentamassiv
force-pushed
the
fix_start_newline_macos
branch
2 times, most recently
from
1d0aa0c to
3f780a2
Compare
pentamassiv
force-pushed
the
fix_start_newline_macos
branch
from
3f780a2 to
b460af2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #260
I am not sure if there is an issue with the rust bindings or the underlying system API, but there is an issue entering strings on macOS that start with a newline character. The workaround will check if the string starts with a newline and will instead simulate the return key. I hope it does not cause any unexpected side effects