DON'T Use the File Explorer in VS Code!

Find better ways to work files than using the File Explorer in VS Code!

**DISCORD**

**STAY IN TOUCH 👋**

**QUESTIONS ABOUT MY SETUP**

[pictzone]

Another great tip is to change the file tree indentation. There's a setting for it. Trust me, larger indentation will help you avoid getting lost in sub-folders and always know how deep is your file in the overall structure.

[alancampagnaro]

All (F1, Ctrl+Shift+P, Ctrl+P, Ctrl+G) actually open the same search box, just with a different prefix, ">" for search command, ":" for line number and no prefix for search file.

[mikestevensdesign]

Thanks for the tips! Getting lost in the file tree is one of my biggest pain points in vscode. Those extensions will really help declutter my window and help keep my zen...once I get use to using them :)

[babyboie]

In large projects it can take vocode longer to filter files where your waiting a bit after you enter the file name for it to appear int the command pallet but generally true I have all these extensions and I love my workflow great tips!

[jongeduard]

Thanks for the tip. I would not say Don't use the File Explorer, but use better tools instead, since it still gives you a handy overview at certain moments, but that's just my nitpick.
File Utils seem a great idea, and possibile the advanced new file plugin. However, I think I am not going to replace my normal new file keybinding, because I do not always want to save a file, because in many cases I simply use new file tabs to temporarily store tekst fragments that I don't want to save in my project.

[henrikstanleymortensen]

A tiny shell tip. Instead of typing out "clear" you can simply use the shortcut ctrl + lower case L while you are in the terminal. This does the same but does not require you to type out the entire thing :)

[ShellBryson]

Great video. I’m on Mac. I mapped a double-tap of the left shift key to bring up the command palette as (for me) it’s a less awkward key combination. Does require the macOS BetterTap app as it allows you to have application specific key combinations with delays (so left shift, and if a second press within 300ms, send Command P if VSCode has focus). Small things, huge time saver!

[voidmind]

BTW, you can type Crtl + L on any terminal window (not just VS code), to clear the terminal. I die a little inside each time I see a YouTuber types the clear command.

[bulentgercek]

The biggest problem with assertive "don't use this" clickbait titles is that their suggestions as a solution inject tons of unnecessary information by saying "download this", "upload this". I respect the information, but saying don't use file explorer is purely personal preference.

[martijnenco]

I disagree a bit.
I think the file tree in vscode is good. But whats bad is using the mouse..
In my project setup most files for a feature are in the same folder. So the search would be way more work then just getting the next file up in the file explorer.
Just use shortcuts. Thats what boost productivity dont use the mouse or atleast as least as possible

[uomek]

seems like needing to know/use a lot more stuff just so you can not use the file explorer to recapture the screen space....to avoid hide/unhide file explorer. Its ok to use your mouse sometimes.

[davidjohnston]

cmd-p and ctrl-p are for bringing up the print dialog. Using it for file search is evil.

[nhall]

I fail to see the reasoning to completely avoid the file explorer. If the purpose is to optimize efficiency and speed, I believe the same can be achieved by using keyboard shortcuts within the file explorer. It's simple to quickly navigate to a specific location within the file explorer, and execute various CRUD operations such as delete, rename, create new file, and more, solely relying on keyboard shortcuts without the need for any additional extensions.

In my opinion, a better argument would be to advocate for the use of the correct tool for each task. Most of the time, there is no need to rely on the file explorer to locate files, mainly when one is already familiar with the file name or parts of the path.

[aCatSiki]

0:55
I use CTRL + E
CTRL + R to open recently opened files, folders, workspaces, etc..

F1 and CTRL + P does the same thing. Open the command palette

[smith]

I have all the extensions and all the shortcuts you mentioned. But still I need file explorer time to time because it's easy to get lost in large projects. I usually keep the file explorer in hiding by pressing "Ctrl + B". With the same command, I can bring out the file explorer.

[christopheanfry]

Love it. Will use those tips!!! So many possibilities in vs code can’t imagine using another code editor.

[melissas]

I love adanced-new-file I saw it mentioned in one your older vids, and I will never not insalls this extension. Saves me so much time.

[mickmister]

I like the piece about key bindings. I'm curious what settings, key bindings, and extensions you use throughout your setup. Thoughts on doing a deep dive or summary of this?

Edit: Sounds like the cheatsheet you mentioned at the end. I submitted this just as I got to that part of the video haha

[ioannistheodoridis]

Sorry to burst your bubble but you are actually missing out on features if you only open the files one by one. For some reason, marking problems inside the code doesn't work if you don't open the folder in vscode.
You can hide the file explorer with one click. I never have any of the problems you are describing

[nikfp]

Thanks James! Saving this for the times when I need to work in VSC.