Don't Use the Sidebar in V…

0 0
Read Time:36 Second



If you want to write code faster, don’t use the Sidebar in VS Code. It will slow you down! As a developer, your goal should be to keep your hands off of the mouse as much as possible. To do that, you should learn to use the built-in shortcuts in VS Code as well as a few amazing extensions. Learn how you can work with your files in VS Code without using the File Explorer or the Sidebar.

Advanced New File Extension –
File Utils Extension –

FREE VS Code Cheat Sheet –
Learn Everything About VS Code –
_____________________________________________

Newsletter 🗞
Interested in exclusive content and discounts? 🤯 Sign up for the…

source

This post was automatic generated with this wp-automatic-plugin

Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %
Top 5 Free Ai image generator … Previous post Top 5 Free Ai image generator …
10 Best Elementor Themes on TemplateMonster Next post 10 Best Elementor Themes on TemplateMonster

37 thoughts on “Don't Use the Sidebar in V…

  1. What do you think about vim extension for vscode ?
    I tried it (I am not a vim user so not used to it), very interesting, big potential but for some reason I can't stick with it and always disable the extension at some point. And then sometime I'm like arf I could have done that without my mouse if I used vim extension. it's kind of a dilemma for me

  2. In addition to ctrl+W, ctrl+shift+T undoes close tabs like ctrl+Z undoes actions.
    In addition to ctrl+tab, adding shift to that reverses the selection direction if you keep pressing tab.
    Similarly, ctrl+pgup switches you to the tab to the left (pgdn goes right) cycling to the end (beginning) if it's reached and adding shift to this moves the tab you're in currently in that direction but doesn't cycle. This also cycles through split views as well but the shift modifier will not move across views, see below.
    Lastly, ctrl+alt+right arrow moves the tab to the right split view (left arrow left) or creates a new view if you're at the end. The UI gets really janky if too many are open, probably dependent on your monitor size. I can get up to 6 horizontal views before things start breaking: there's a scrollbar that's hard to access, file contents remain where they are instead of following their view when that scrollbar is used, things overlap the sidebar, etc.

  3. Additional tip – if you want to switch instantly between open tabs (without having to see the list of files):
    Ctrl + Page Up
    Ctrl + Page Down
    Will jump back and forth between your currently open source files. Same shortcut works for most tabbed web browsers too.

  4. One thing I don't get is why are you OK with pressing Ctrl+Shift+P for just opening Command Palette? It's PITA.
    F1 should have been the most mentioned go-to shortcut, IMO!

  5. CTRL + K + C => comment line or block of lines
    CTRL + K + U => Remove comment

    CTRL + 1 or CTRL + 2 or CTRL + 3 (….) => switch between views
    CTRL + ALT + ARROW_KEYS => Move open file for other view

  6. Can someone tell me why people use different IDES for different programming languages instead of using VS Code to write variety of languages?
    In my opinion, i think it is due to the white output which make it hard to look in terminal

  7. Don't learn too much shortcuts, one day you will work with different program that don't have these shortcuts.
    now I'm trying to write some code without vim keybindings (because reasons!), and I find it much harder to unlearn shortcuts than pick them up.

  8. (“Cmd + K”, “M”) Is a really good one for changing the file type. When I create new files, I generally do:
    1. (“Cmd + N”) New File
    2. (“Cmd + K”, “M”) Select File Type
    2.5 (I often write the code here before moving it)
    3. (“Cmd + Shift + P”, “Move”) move the file to right directory

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!