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-click selection matches some escaped characters #45395

Open
anticore opened this issue Mar 9, 2018 · 2 comments
Open

Double-click selection matches some escaped characters #45395

anticore opened this issue Mar 9, 2018 · 2 comments
Labels
editor-wordnav Editor word navigation issues feature-request Request for new features or functionality under-discussion Issue is under discussion for relevance, priority, approach
Milestone

Comments

@anticore
Copy link

anticore commented Mar 9, 2018

Issue Type: Bug

If you have a string with the "\t", "\n", etc. sequences followed by a word, double-clicking the word will select the escaped character as well:
screenshot from 2018-03-09 10-10-29

VS Code version: Code 1.21.0 (9a199d7, 2018-03-07T11:01:43.521Z)
OS version: Linux x64 4.10.0-42-generic

System Info
Item Value
CPUs Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3142)
Load (avg) 0, 1, 1
Memory (System) 15.56GB (3.82GB free)
Process Argv /usr/share/code/code --unity-launch
Screen Reader no
VM 0%
Extensions (7)
Extension Author (truncated) Version
vscode-icontheme-nomo-dark be5 1.3.5
vscode-eslint dba 1.4.7
githistory don 0.4.0
auto-close-tag for 0.5.6
docthis joe 0.6.0
python ms- 2018.2.0
color-highlight nau 2.3.0

(1 theme extensions excluded)

Reproduces without extensions
@vscodebot vscodebot bot added the new release label Mar 9, 2018
@vscodebot vscodebot bot removed the new release label Mar 13, 2018
@rebornix rebornix added the under-discussion Issue is under discussion for relevance, priority, approach label Sep 6, 2018
@rebornix rebornix added the editor-wordnav Editor word navigation issues label Oct 24, 2019
@Louis-DR
Copy link

Louis-DR commented Jun 19, 2020

I also experienced this issue. If we could specify mutliple character length patterns in editor.wordSeparators, it would solve this issue and also allow things like double underscore __ to be considered a word separator but not a single underscore _. This is useful with snake case : assert_main_loop__wrong_input for instance.

@rebornix rebornix added this to the Backlog milestone Sep 30, 2021
@rebornix rebornix removed their assignment Sep 30, 2021
@jrieken jrieken added the feature-request Request for new features or functionality label Oct 1, 2021
@Lexikos
Copy link

Lexikos commented Jul 12, 2022

I regularly encounter this problem both with word select and word delete (ctrl-backspace).

I think that it would be ideal to have default behaviour that respects the boundaries already determined by the syntax highlighter.

In my case the escape sequence is usually `n rather than \n.

If we could specify mutliple character length patterns

If "patterns" means regex (as opposed to just strings of characters), perhaps it would cover #54571 and #147651 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor-wordnav Editor word navigation issues feature-request Request for new features or functionality under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

5 participants