Skip to content
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

Double-clicking to select text in an editor should respect casing (as developers see casing) #22320

Closed
estaylorco opened this issue Mar 9, 2017 · 4 comments
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@estaylorco
Copy link

  • VSCode Version: 1.10.2
  • OS Version: OS X (El Capitan) 10.11.6
  • Language: Agnostic

Consider the following text samples:

  1. messageQueue (camel)
  2. message-queue (kabob)
  3. MessageQueue (Pascal)
  4. message_queue (C)

As it stands now, when I double-click text formatted as #2 above, "words" within the text select independently of the rest of the text, as we would expect (the hyphen provides a natural breaking point).

But that doesn't happen in the caseS of #1 , #3, and #4. Yet, from a developer's perspective, there's no difference really.

It would be nice if there were a setting that would allow us to treat cased words within text (with no intervening whitespace) as separate "words". In the case of #1 above, for example, double-clicking within "Queue" would select just Queue, etc. Additionally, in a manner similar to clicking in Microsoft Word, if we triple-click, then the entire text would be selected without respect to casing.

I seem to recall being able to do this years ago in Visual Studio (though I think we had to have the ReSharper extension).

Thank you for your consideration...and for a great job!

Eric

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Mar 9, 2017

You can add _ to the editor.wordSeparators setting for your 4th case to work.

For the other 2 cases, I'll leave it to @alexandrudima to comment

@ramya-rao-a
Copy link
Contributor

@estaylorco
Copy link
Author

@ramya-rao-a Thanks for the head-up on editor.wordSeparators. Also, the link you gave to the subword navigation plug-in is useful. I just installed it.

But this does need to be tied in to double-clicking as well, not just keyboarding (at least so far as selection goes.

Thanks, again!

@alexdima alexdima added feature-request Request for new features or functionality editor labels Mar 28, 2017
@alexdima alexdima added this to the Backlog milestone Mar 28, 2017
@alexdima alexdima removed their assignment Mar 28, 2017
@alexdima alexdima added the *out-of-scope Posted issue is not in scope of VS Code label Sep 20, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 20, 2018

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

3 participants