-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Implement word part move and delete for issue #46203 #48023
Conversation
Hello all! I can see that CI is failing due to a formatting issue, but I haven't been able to find any information on how to fix it. Is there some sort of tool I can run to find my errors? Thanks! |
I wonder how you were able to commit since our pre-commit hooks should have failed. To fix, open these files in VSCode and run |
My apologies. After I couldn't figure out what the errors meant, I disabled the pre-commit check in the hopes someone would look at my pull request and help me find the problems. In hindsight, I probably should have just posted a question first. Thanks for the tip! |
Thank you! |
So glad to see this being folded into vscode! After trying this out in insiders I have couple of minor comments: Cursor location is non-symmetric for left versus right movementsThis implementation puts the cursor in slightly difference places compared to sublime/intellij/the extension I have been using (https://github.com/ow--/vscode-subword-navigation) in sublime/intellij/the extension they all stop at the locations marked with | regards of it the cursor is coming from the left or right:
In this extensionif from the right Notice that the cursor will be in different asymmetric locations when going left or right. Things get a bit more complicated in sublime vs intellij when there are multiple consecutive symbols, in sublime it appears as though the cursor will treat any block of symbols as one word (e.g. Subword navigation doesn't appear to work in input box like the file-rename box in the file explorerI could be mistaken on this but it looked like it wasn't working there when I tried it. |
+1 - it should work in the file input and other non-editor boxes, otherwise ow--'s plugin is good enough. I believe it was not possible in the plugin due to API limitations, which a native solution should be able to overcome. |
Not sure how it should work in this case: |
#46203