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.

Sign up for GitHub

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

Jump to bottom

Add support for exact filenames for searches #56

Closed
rpaquay opened this issue Feb 7, 2020 · 1 comment
Closed

Add support for exact filenames for searches #56

rpaquay opened this issue Feb 7, 2020 · 1 comment

Comments

@rpaquay
Copy link
Contributor

rpaquay commented Feb 7, 2020

Currently when typing foo in File Paths of Code Search tool window, the search is implicitly transformed to *foo* (basically a sub-string match). This is useful in most cases, but there are cases where searching for a specific filename can be useful (e.g. Makefile).

To enable these "exact" match searches, the proposal is to allow using double quotes around the path.

So, "foo" would search only files that are exactly named foo
@rpaquay rpaquay mentioned this issue Feb 10, 2020
Open
rpaquay added a commit that referenced this issue Feb 10, 2020
@rpaquay
Add support for exact filenames for searches
d392dd1 
In the `File Paths` text box of `Code Search`, double quotes can now be used
to prevent implicitly surrounding simple searches with "*".

For example,

* Typing `foo` results in matching any filename containing `foo`
  (e.g. `barfoo`, `foo.h`, `bar.foo`

* Typing `"foo"` results in matching files that are named exactly `foo`,
  and nothing else.

Fix feature request #56
rpaquay added a commit that referenced this issue Feb 10, 2020
@rpaquay
Add tests for #55 and #56.
eee7936
@rpaquay
Copy link
Contributor Author

rpaquay commented Feb 12, 2020

Fixed in (pre)release 0.9.32 (https://github.com/chromium/vs-chromium/releases/tag/v0.9.32)

tcwz pushed a commit to tcwz/vs-chromium that referenced this issue Feb 14, 2020
@rpaquay
Add support for exact filenames for searches
b7fc2a5 
In the `File Paths` text box of `Code Search`, double quotes can now be used
to prevent implicitly surrounding simple searches with "*".

For example,

* Typing `foo` results in matching any filename containing `foo`
  (e.g. `barfoo`, `foo.h`, `bar.foo`

* Typing `"foo"` results in matching files that are named exactly `foo`,
  and nothing else.

Fix feature request chromium#56
tcwz pushed a commit to tcwz/vs-chromium that referenced this issue Feb 14, 2020
@rpaquay
Add tests for chromium#55 and chromium#56.
6393b88
rpaquay added a commit that referenced this issue Jun 9, 2020
@rpaquay
Add tests for #55 and #56.
b966d1b
rpaquay added a commit that referenced this issue Jun 9, 2020
@rpaquay
Enable usage of more than 64 CPU Cores
6c7eb6b 
See https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/thread-useallcpugroups-element

Fixes bug #56.
@rpaquay rpaquay closed this as completed Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rpaquay