Fix double clicking an identifier selecting glyphs #20
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
|
Oh, thanks! I was wondering how to do this. |
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.
This change defines every Uiua glyph as a word separator. This fixes an issue I have where double clicking an identifier to select it would also select nearby glyphs, which often results in unintentionally deleting some necessary logic when refactoring code. This change also excludes
!and&from separators, because they are also often a part of an identifier and you would want to select them when double clicking an identifier.As a bonus, when I was browsing the code, I noticed that the identifier definition in
uiua.tmLanguage.jsondid not include negative subscripts, so I also added those.