DON'T Use the File Explorer in VS Code!

much more faster and without extensions: use the terminal

Man, I gotta say, I love your videos and your content, and I actually do really like this -- but I have encountered one edge case pitfall. I'm working at a company now that is going all-in on a "low-code" solution for end users in our industry. It's a solution and ecosystem that is based on widgets, and according to the code standards laid out by this solution's creators, every widget must name its core files the same way. So if you're working with multiple widgets at once -- which we frequently have to do because many times these widgets aren't used on their own, but in a mini-ecosystem of sorts -- if you use this method, you'll frequently end up opening a file that's named what you want, but it is in a completely different widget, and can really screw you up sometimes.

Just a warning to other devs, make sure you're paying attention to the entire file path too!

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.

What font do you use bro ?

my english bad 😔 but how to set open folder only at "dekstop" mine when i open new folder why they show "🏠 ken" user at mac. ugh i think ppl dont know what am i saying 😭

Thanks for the tips James!

at that point just use neovim with plugins

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.

As you showed in your video I already have ctrl+shift+` for new terminal. But I see no way to create another shortcut which triggers when=terminalFocus. I don't want to edit the existing keybinding. Can you tell me how you added a new keybinding for ⌘+N and also have the ^+shift+` for the same action?

Have you seen those projects that have an index in every folder? :P

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

How is called the shortcut option to tab through the terminals? I couldn't find it by myself.

I should send this to my coworkers :P

Just a matter of preference. For me, one of better things is that file explorer is there and it's enabled.

This is really useful. Thanks 😀

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

isn't the more "chad" way to just do all of this in the terminal?

Thanks for the recommendations! The default new file command was super annoying.

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.

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 :)

Thank you, this was very useful for me!

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!

Thanks for sharing

Put it on the right side, you will never lose a space

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.

what vscode theme you are currently using please?

Very nice inspiration. I switch totally to Vim and use the FZF file finder ;)

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

Pat Benatar gave up the rock-n-roll lifestyle to create VSCode extensions?

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

What about browsing files? "I dont know where that one file is, or what its named, but I'll see it once I browse around the project." Or any variation of that scenario where you don't have enough context to use fuzzy find to search for your file.

file utils able to create new file too :)

Thanks. But I use what I want.

You need context. The shortcut idea only works when the workspace has unique names across all projects. And when it doesn’t, the fact that you’re seeing the path in the command window, is the exact same thing as using the explorer. There’s nothing gained here.

Ctrl + B

I find it really usefull for navigating an vps

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.

I've been trying to use Ctrl+P go to file for so long, but old habits die hard. I'll probably just keep using the file explorer forever :)

Overly complicating a simple thing

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.

come to VIM

Nah, I use my time clicking around the file explorer as a break

🙂... I think imma stick with the default File Explorer.

This is awesome James! Loves the video. I was curious as to which font style and size do you use in VS Code?

James that shirt is a baggy on you have you been losing weight

crazy useful... TNX

Dude you need to have a good sleep or smth:)

thx

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!