DON'T Use the File Explorer in VS Code!

Find better ways to work files than using the File Explorer in VS Code!
FREE VS Code Cheatsheet - learn.jamesqquick.com/vs-code...
*DISCORD*
Join the Learn Build Teach Discord Server 💬 - / discord
*STAY IN TOUCH 👋*
Newsletter 🗞 - www.jamesqquick.com/newsletter
Follow me on Twitter 🐦 - / jamesqquick
Check out the Podcast - compressed.fm/
Courses - jamesqquick.com/courses
*QUESTIONS ABOUT MY SETUP*
Check out my Uses page for my VS Code setup, what recording equipment I use, etc. www.jamesqquick.com/uses

[@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.

[@justingiovanetti]

Agreed. That's the first setting I change.

[@JamesQQuick]

Yeah I've played around with that in the past. definitely helpful for visibility

[@somerandomchannel382]

Not sure what you mean but you can lowkey type afew letters of the sub folder you wanna work in, Enter, type a new file name, Enter again. done : )

[@MMH94MMH]

@@somerandomchannel382 he means, *Workbench > tree:indent* option in VSCode settings

[@babyboie20]

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!

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

[@JamesQQuick]

Definitely takes some time to adjust but I think they’re super helpful! Glad you enjoyed it :)

[@guilhermemm-dev]

@@JamesQQuick what vscode theme you are currently using please?

[@JamesQQuick]

@@guilhermemm-dev This is my own theme. James Q Quick :)

[@naishe]

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?

[@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!

[@JamesQQuick]

Oh that's a really interesting idea. I might need to check that out!

[@melissas4659]

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.

[@JamesQQuick]

haha yeah same!

[@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.

[@christopheanfry2425]

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

[@JamesQQuick]

It's so amazing!!

[@henrikstanleymortensen4295]

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

[@JamesQQuick]

Someone else mentioned that. Apparently it doesn't actually remove the previous lines it just moves them up or something?

[@shahman1]

it clears them up on linux, on Mac you can press CMD + K to clear the terminal up, and CMD + L will move the lines up

[@daephx]

One thing windows does right is command: cls for clear screen. Setting that as an alias is good enough for me, ill be its a bit slower than ctrl-l

[@AmodeusR]

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

[@nikfp]

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

[@JamesQQuick]

Yeahh!!

[@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 KZbinr types the clear command.

[@Chiny_w_Pigulce]

clear and Ctrl+L don't work the same way

[@bulentgercek]

@@Chiny_w_Pigulce How?

[@Chiny_w_Pigulce]

@@bulentgercek Ctrl+L only moves the screen so that the current line is at the top of the terminal's screen. Clear removes all previous lines.

[@JamesQQuick]

WHAT?!?! I had NO IDEA Lol

[@squ34ky]

This tip is great... until you hit the scroll wheel on your mouse and see that CTRL+L only hides the previous commands..

[@alancampagnaro8511]

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.

[@JamesQQuick]

Yeah that makes sense

[@jongeduard]

Yep, and that can be useful for example when you accidentally did or dit not press the Sift key when pressing the Ctrl and P key. You don't have to Esc first, but just type or delete the colon or more-than-sign indeed.

[@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

[@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

[@CURIOSITYcapital]

Neovim is my editor of choice

[@DNAwastaken]

I want to start using neovim

[@DNAwastaken]

I’m currently learning DVORAK to go with NeoVim

[@ofeenee]

I’ve just started transitioning to nvim, however some things I’m used to doing with vscode isn’t available by default in nvim. For example: - toggle comment line/block in different files types. I’ve installed tpope/commentary plugin, however, it doesn’t work as well as vscode, and not at all with svelte/kit (the main framework I use) - settings up intellisense/autocomplete alongside github copilot can get tricky, with shortcuts and/or shadows of suggestions overlapping over each other is annoying. I’m not a big fan of heavy customization an IDE, i like it close to stock and simple, but these two things to me are important. Any ideas or tips you can suggest regarding these two? 🙏

[@CURIOSITYcapital]

Neovim is awesome with all the plugins and keybindings if you guyz need my neovim setup config plz let me know

[@Dev-Siri]

ok

[@krishjaiswal5243]

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

[@JamesQQuick]

Awesome! Here's my uses page which has all those details. www.jamesqquick.com/uses/ My font is Cascadia Code and my size changes

[@nhall78]

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.

[@uome2k7]

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.

[@andreh.9300]

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

[@mickmister]

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.

[@cezaraugustomezzalira5230]

Thanks for the tips James!

[@jesper.ordrup]

good tips. but im missing the sveltekit shortcuts. sveltekit: create route etc. They work as commands but they seem to work releative from current selected folder

[@JamesQQuick]

Like SK code snippets you mean?

[@ahmedahmedx9600]

What font do you use bro ?

[@nekathedev]

Thank you, this was very useful for me!

[@smith4591]

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.

[@JamesQQuick]

Yep! Agreed. 95% of the time I use shortcuts but there are definitely times when you need it.

[@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.

[@JamesQQuick]

Yep, definitely my preference. It has served me well. Thanks for comment!

[@davidjohnston4240]

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

[@JamesQQuick]

haha hard to let go

[@ken-bw7by]

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 😭

[@steveliveshere]

This is really useful. Thanks 😀

[@NeverCodeAlone]

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

[@JamesQQuick]

Nice! How are you liking it?

[@NeverCodeAlone]

@@JamesQQuick Awesome. Maybe we can do a YT live sharing. I am starting and totally motivated do go forward!! Have also my first german 11 part tutorial series about it.

[@oszi7058]

I find it really usefull for navigating an vps

[@guilhermemm-dev]

what vscode theme you are currently using please?

[@JamesQQuick]

My personal theme - James Q Quick :)

[@whoopsimsorry2546]

Welcome to vim, fuzzy finder does the same thing, if you don't remember the name just grep some text, if too big for grep, vscode already dead.

[@TomNook.]

I just have a keyboard shortcut to show/hide the side panel, open a file in a split second, no visual clutter, no typing, no having to remember the file name.

[@JamesQQuick]

Yeah I do the same for showing and hiding. The search ability is super low that way for me though. Also I try to avoid the mouse as much as possible

[@michaelchen9310]

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

[@aamindehkordi]

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

[@appuser]

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

[@JamesQQuick]

haha as long as it works for you

[@dannnsss8034]

I'll still use the file explorer... Or maybe there's a better way to visualise it. I hate it when there's like 50 files in one folder and you lose your context within the folder structure. Is there an easy way to close the immediate folder without having to scroll to the root of the directory? Or to close all open folders...

[@mittamoa]

Try Left key while in filebrowser

[@NorthernChimp]

@@mittamoa 👍

[@thecoolnewsguy]

​@@mittamoayou mean left arrow?

[@mittamoa]

@@thecoolnewsguy yes. with the arrow keys you can navigate up and down the file tree as well as open and close the currently selected directory. if you are within a directory and have a containing item selected, to close the current directory you are in, press left arrow key to be exact. Now i will leave you alone 😉

[@pictzone]

You can also close all open folders with ctrl + shift + p and then type collapse

[@viniciusfranco1241]

Thanks for sharing

[@JamesQQuick]

Absolutely. Thanks for watching!

[@StankoOpacic]

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

[@JamesQQuick]

Nice! Whatever works for you!

[@UmanPC]

crazy useful... TNX

[@JamesQQuick]

Yess! Glad to help

[@squ34ky]

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

[@JeremyKolassa]

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!

[@JamesQQuick]

Fair enough! I definitely imagine there are edge cases. Thanks for sharing!

[@SuperKidontheblock]

I use these shortcuts and they're such time saver especially when pair programming

[@JamesQQuick]

Yeah! Love it!

[@MMH94MMH]

Thanks for this video James, I think no need to install extra extension for deleting and renaming, i prefer to use *del* button delete and *F2* button to rename.

[@JamesQQuick]

But that only works if you're inside of the file explorer right? My problem is that is takes up space and isn't very searchable to find the file you're looking for

[@MMH94MMH]

@@JamesQQuick i have tested the file utils extension which you mentioned in this video, and it offer the rename and delete action in the context menu as well, no need to use the command palette

[@JamesQQuick]

@@MMH94MMH The context menu in the file explorer? I know you can do all that, but my preference is to avoid the file explorer because I think it's much slower and takes up space.

[@MMH94MMH]

@@JamesQQuick not in file explorer, when you right click inside the opened file, you still save the space and do it even faster. thanks for sharing this extension ✌

[@JamesQQuick]

@@MMH94MMH Ah ok now I understand. I still prefer not to use the mouse when possible because I think anything on the keyboard is much faster. Great callout though.

[@ioannistheodoridis4322]

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

[@JamesQQuick]

What do you mean by marking problems? Also you mentioned opening files one by one. Do you often open multiple files at a time?

[@kikisbytes]

I should send this to my coworkers :P

[@JamesQQuick]

Please do lol

[@michalnowak2181]

thx

[@heygema]

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

[@JamesQQuick]

That is an option! Still takes up space though if your overall width isn't that great though.

[@cachipum]

much more faster and without extensions: use the terminal

[@iblamefps]

at that point just use neovim with plugins

[@hendrykhoza4782]

come to VIM

[@JamesQQuick]

lol haven't been able to make that jump

[@Learnbynet]

losing space ? it maybe time to code on a 50p tv 4k !

[@JamesQQuick]

Maybe so 🤷‍♂️

[@alexmercer416]

No use.

[@JamesQQuick]

Hmmm any more specific feedback? Do you alternative workflows you prefer?

[@alexmercer416]

@@JamesQQuick normal side panel only works faster, and most of the time we donno what is the file name, so by going through side panel works. saving milliseconds doesnt work here...

[@JamesQQuick]

@@alexmercer416 If that works for you that's great. I find the complete opposite for me. I know the name of my files 95% of the time. I think that's pretty common for a project that you work on for any amount of time. So, for me, it's much more like seconds every time I open a file. It definitely changes my workflow for the better.

[@ColtonA-iq9bv]

Thanks. But I use what I want.

[@JamesQQuick]

Fair enough! Whatever works for you :)

[@mikamulperi]

Ctrl + B

[@JamesQQuick]

Yep! Use that all the time!

[@justingiovanetti]

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.

[@JamesQQuick]

Not sure what you mean by across projects. Do you keep multiple projects open at a time in VS Code?

[@justingiovanetti]

@@JamesQQuick Well … yea, sometimes. Sometimes I’ll have multiple project in a workspace. That’s not really the point. A single project can technically have files in it with the same name. All good :) … great videos though man! Good stuff.

[@pictzone]

@@justingiovanetti if your files are like that you need to change your approach

[@justingiovanetti]

@@pictzone fantastic advice.

[@pictzone]

@@justingiovanetti talking about the files in one project, not multi-project

[@JohnMcclaned]

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

[@JamesQQuick]

haha that's a good idea!

[@snatvb]

file utils able to create new file too :)

[@JamesQQuick]

I need to double check that. There was a specific reason I didn't do that lol

[@snatvb]

@@JamesQQuick for me works fine)

[@snatvb]

@@JamesQQuick Hi again, I tried to use new file from file utils and it doesn't work without any response, new adwanced file doesn't work for me too, because tries to scan my codebase - I have 36MB source code (huge project), so, for me no solution to make file easier than with explorer

[@hri7566]

is this primeagen bait

[@JamesQQuick]

I guess so 🤷‍♂️

[@kneelesh48]

Overly complicating a simple thing

[@JamesQQuick]

Maybe, but it's certainly worked well for me.

[@Elias-vs2dx]

At this point just use neovim

[@Dev-Siri]

who asked

[@JamesQQuick]

What do you love about neovim?

[@thecoolnewsguy]

No

[@JamesQQuick]

@@thecoolnewsguy hmmm...

[@thecoolnewsguy]

@@JamesQQuick life is too short to learn keybindings and configure neovim

[@abraham_o]

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

[@JamesQQuick]

Nice! Any particular reason why?

[@shu9460]

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

[@JamesQQuick]

Probably just baggy lol

[@seancooper5007]

vscode is a crutch

[@JamesQQuick]

lol what do you use?

[@metamodern7648]

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

[@JamesQQuick]

Why do you say that,

[@metamodern7648]

@@JamesQQuick no offence, useful material, but maaan you look tired:( Maybe it's the lighting though

[@JamesQQuick]

@@metamodern7648 hmm yeah I think I have natural bags under my eyes which is unfortunate. I promise I get lots of sleep and drink lots of water though!

[@metamodern7648]

@@JamesQQuick take care:)

[@aleksandarpopovic3615]

delete cmd+backspace delete selected file/dir "key": "cmd+n", "command": "explorer.newFile", "when": "explorerViewletVisible && filesExplorerFocus && !inputFocus" "key": "shift+cmd+n", "command": "explorer.newFolder", "when": "explorerViewletVisible && filesExplorerFocus && !inputFocus" no need for extensions

[@JamesQQuick]

That's very hard to read in YT comments lol