Double-click should select #ff0000

[BobPritchett]

Type: Feature Request

[ "black", "white", "#CC3733", "#FCA103" ]

I want to double-click in "CC3733", Ctrl+X, and then double-click on "black" and Ctrl+V, and have it work. If you do that now, you get:

[ "CC3733", "white", "#", "#FCA103" ]

Which creates two manual clean-up steps.

Please use code-aware logic for double-click, Ctrl+Right and Ctrl+Left, not English prose logic. # is part of the 'word' I'm double-clicking on in JavaScript or HTML or CSS.

In a URL # might make sense as a word separator, but not in "#ff0000". Changing 'Editor: Word Separators" isn't enough -- there should be language/context-aware logic.

VS Code version: Code 1.75.1 (441438a, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

[aeschli]

Double click is not based on separators that you can configure with editor.wordSeparators.

Note that the language (JavaScript) also doesn't know that "#FCA103" is a color. It's just a string literal. Ther's nothing really code aware that can be applied, except than teaching the double click selector the color pattern.

[BobPritchett]

Yes, from a purist point of view, #ff0000 is just a text string. But from a practical point of view, it's an atomic token with specific meaning -- which is why VS code can even insert a little colored swatch next to it, which is clearly 'special' treatment for that particular string pattern.

I am suggesting that the user experience would be enhanced by having double-click be much more aware of common literals and even the syntax tree so that selection is more useful. This is an action we perform constantly, and there's lot of specialized intellisense and auto-completes and lint rules for all kinds of obscure stuff, and cursor is much more common, and worthy of equal attention.

[alexdima]

@BobPritchett I cannot reproduce. The following works for me:

// the default with # missing
"editor.wordSeparators": "`~!@$%^&*()-=+[{]}\\|;:'\",.<>/?"

Kapture.2023-02-20.at.16.51.37.mp4