-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Add CamelHumps support #541
Comments
+1 Although I would prefer it Resharper Style where it changes the behavior of the standard Ctrl + Left and Ctr + Right hotkeys. |
+1 |
Someone already did. As for the key bindings, you can always change the default. |
The plugin works fine! However, this is such a default functionality (at least in other IDEs). |
Sorry for the spam folks but in the interest of searchability (because it took me quite some time to find this via other closed issues), I'll add a few keywords here: subword navigation, word navigation with camelCase, move by word break on capitals, wordSeparators. And FWIW, I am happily using the extension which works wonders, and allowed me to restore sublime text-like functionality using alt[+shift]+left/right/del/backspace. |
I think both full-word navigation and subWord (or camelHumps style) navigation are very useful features. Currently I'm also using this plugin https://marketplace.visualstudio.com/items?itemName=ow.vscode-subword-navigation to enable the sub word navigation. I'm using these key mapping: But I think it should be added to core instead of using it as a plugin as all the popular editors like: Sublime, Atom, Webstorm etc. support it out of the box. |
Ou, I really miss that functionality... I'll use the plugin, but this is the base functionality, it should definitely be the part of the editor. Thanks! |
i hope have this feature soon, sorry that i can't help anything just only wait for |
+1 This feature lacks in vs code but should be standard for any modern file editor related to coding |
+1 |
Just linking this an issue from this very nice extension that adds the functionality to the editor, to see if anyones know if there are more points in the API to hook into allowing it to work in search / rename / other input type boxes: https://github.com/ow--/vscode-subword-navigation/issues/12 |
Still not done? :( |
I switched from another text editor that I had been using for a long time because Visual Studio Code seems to be better. But now, I'm starting to miss this functionality :/ |
There currently seem to be three extensions that provide this functionality: https://github.com/ow--/vscode-subword-navigation This functionality should really be part of core. FWIW, as a Mac user, shortcuts I'd expect:
These are the keybindings Sublime Text, as well as the "Subword Navigation" plugin (first one linked above), use. |
+1 |
This feature has been added by the PR #48023 and will be available in the It seems that @alexandrudima is using the issue #46203 as the source of this addition, just to point it out because there is recent activity here, which seems to not know this has been added (and is even in the Insiders already!). |
Yes, thanks to @brentwang23 for the PR! Here is an example for how you can bind the new commands:
|
@alexandrudima do we need to add this to our user config or will these be added to the defaults when 1.25 is released? If they won't be added to defaults, why? Thanks! Edit: just saw 1.25 was just released. It does have defaults but they're not ideal on Mac. The defaults on Mac should be what you provided above (ty!) but it looks like they're what's listed in the 1.25 release on all platforms. i.e. move subword right is "ctrl+alt+right" instead of "ctrl+right". |
Nor are they ideal for Windows. Not really sure why |
The fix released in |
Thanks @V-ed I'll track that issue. 👍 |
Great progress. It'd be nice if this feature were extended to allow sub-word selection with the mouse too as IntelliJ does. |
Like atom it is a good feature to move cursor around parts of a camel cased word with Alt+Right and Alt+Left
The text was updated successfully, but these errors were encountered: