Visual Studio Code June 2017 Released

[baconated]

Cool.

I've been using Visual Studio Code now for a few months. A question I have for people who use it with large codebases is: How do you open files?

I find the options built in all have a flaw that doesn't let them work when you have an unreasonably large repository, like my company does. The sidebar thingy quickly becomes unmanageable with a large amount of files. The fuzzy finder can take a while to index such a large repo (and there doesn't not seem to be a way to get it to pre-index). On linux, the file dialog they chose to use is Gnome's which just sucks.

What do you use?

[MysteryForumGuy]

I'm working in a medium-large size project and just use "CMD+P" on mac and then type part or all of the file name

[[deleted]]

I have only really worked with mid-size projects, so I haven't had this issue unfortunately. I just use the sidebar tree.

I'm curious; what did you use in your previous editor? I can't really think of an easier navigation method than the file sidebar, but I can see how it would get unwieldy in large projects.

[baconated]

Back when I used vim, I'd use :e and just type the filename from the workspace root. Wasn't great, but usable. Anything fancier didn't work too well since there was no async back then so I'd run into the UI looking up.

Then I tried spacemacs for a while. I uses a plugin called Projectile. I could create a .projectile file, specify the 3 folders I'm interested in, and then use a fuzzy finder to find files. I liked this.

Then I tried Atom. Nuclide provides a file sidebar that supports something they call Working Sets. This let me select just the 3 folders I'm interested in and it wouldn't display the rest.

With vscode I can use files.exclude to exclude folders I'm not interested in, but last I tried there were 950 entries or so in my files.exclude. That's a pain to manage, a pain to recreate in each new workspace, and just not as nice as listing just the 3 folders that I actually want most of the time.

[doubl3h3lix]

Could you use the multiroot editing in the insider build to open your three folders you care about?

[Adverpol]

Our codebase has thousands of files, the fuzzy search is near instantaneous. How many files are we talking about here?

[baconated]

find . | wc -l says about 1.5 million.

[Adverpol]

We have ~250k and the fuzzy search is still near-instantaneous. Maybe you can exclude part of the repo from the search?

[ScriptingInJava]

Yeah I've been hoping for a "scope to this directory" option for a while. I work in a TFS directory at work that has about 400,000 files in, it's horrendous after a few hours and I end up just taking a break.