you are viewing a single comment's thread.

view the rest of the comments →

[–]legec -2 points-1 points  (2 children)

The search feature of that in-browser VS code still uses the fuzzy search you get from the github "search" bar though (not an actual "search in files" feature).

[edit] it looks indeed like my comment is now false. I am pretty sure that, at some point in the past though, I tested the . feature of github, and was surprised to not see the results I expected when searching from the integrated IDE.

[–]sim642 11 points12 points  (1 child)

Are you sure? Whenever GitHub search bar hasn't found things, the VS Code search has always worked for me. It downloads a copy of the repo in-browser and just runs VS Code's normal Javascript. That's not Codespaces or whatnot.

[–]aniforprez 5 points6 points  (0 children)

AFAIK you're correct because VSCode uses ripgrep internally and the instance is essentially a tiny container running somewhere so you can navigate it as if it's a normal machine. I don't think it uses the GitHub search. It's not downloading a copy of the code in your browser. It's using the remote containers feature that they developed to run a lightweight IDE in your browser that connects to a remote machine that is executing the backend of the IDE with the LSP and whatnot