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
rebornix opened this issue
Sep 25, 2018
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugterminalGeneral terminal issues that don't fall under another labelupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
In the editor, CODE with march word turned on will not match anything in CODE_OF_CONDUCT as _ is seen as a whole word but in terminal find widget, it matches CODE. IMO we don't have any word separators set for the terminal but having different behaviors of find widget options seems weird.
The text was updated successfully, but these errors were encountered:
These are the non-word characters right now: ~!@#$%^&*()_+-=[]{}|\;:"\',./<>? and back-tick. Looks like underscore should be removed. Are there any others that stand out?
Tyriar
added
bug
Issue identified by VS Code Team member as probable bug
and removed
under-discussion
Issue is under discussion for relevance, priority, approach
labels
Oct 5, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugterminalGeneral terminal issues that don't fall under another labelupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
#59267
In the editor,
CODE
with march word turned on will not match anything inCODE_OF_CONDUCT
as_
is seen as a whole word but in terminal find widget, it matchesCODE
. IMO we don't have any word separators set for the terminal but having different behaviors of find widget options seems weird.The text was updated successfully, but these errors were encountered: