You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This extension doesn't seem to consider the editor.wordSeparators setting. I see you are using an API that in theory should consider that setting, but in my usage it doesn't seem to. Specifically if my cursor is in a kebab-case-word I want all of that selected, but it stops at the dash even though dash is not included in my editor.wordSeparators setting. This may actually be a VS Code issue but figured I'd file it here to see if you had any insight.
The text was updated successfully, but these errors were encountered:
The built-in function I use indeed ignores editor.wordSeparators. It does however respect the text document's language settings. See microsoft/vscode#8233 for a discussion about this.
If you change the settings for the filetype you are working with, it should work as expected.
But selectWord still stops at dashes, even though a mouse double-click selects a full kebab-case-symbol.
If I'm reading the issue 8233 you linked above, they are talking about the language definition itself (the definition of clojure support for example), and they talk about wordPattern which does not seem to be an end-user available setting.
Any other tips for me here? I use select word heavily in my editor flow so this is a real nuisance for me.
This extension doesn't seem to consider the
editor.wordSeparators
setting. I see you are using an API that in theory should consider that setting, but in my usage it doesn't seem to. Specifically if my cursor is in akebab-case-word
I want all of that selected, but it stops at the dash even though dash is not included in myeditor.wordSeparators
setting. This may actually be a VS Code issue but figured I'd file it here to see if you had any insight.The text was updated successfully, but these errors were encountered: