Vim in VS Code

Dive into 'Vim in VS Code' and discover practical Vim techniques seamlessly integrated into today's modern coding environment. Join our livestream as we showcase how to leverage the power of Vim keybindings and commands within VS Code to enhance your productivity and streamline your workflow. Learn from our expert hosts as they demonstrate real-world use cases, time-saving tips, and best practices that bring Vim's efficiency to your VS Code experience. Don't miss this opportunity to elevate your coding skills and master the art of Vim in a contemporary development setting.
Chapters:
00:00 Livestream begins
00:44 Welcome to the VS Code Livestream
01:25 Throwback TikTok Thursday
03:09 Welcome Michael Chan
03:34 Vim in VS Code
04:46 What is Vim
11:20 Vim Extension - vscodevim
12:25 Demo
36:51 Vim Graphical Cheat Sheet
53:30 Lightning Round
56:50 Connect and learn more
58:40 Wrap
Community Links:
github.com/chantastic
chan.dev/
/ discord
reactpodcast.com/
Join us for VS Code Day, April 26th aka.ms/VSCodeDay2023
Featuring: Reynald Adolphe (@ReynaldAdolphe), Michael Chan (@chantastic)
#vim #code #vscode

[@datamonster3212]

I started with vim keybinds in VSC, but switched to full Neovim in the end. It's just so nice to be able to do everything from the keyboard.

[@shivanshchaturvedi3337]

hey i am just not able to learn all the short cuts can you tell me exactily how to begin??

[@GregRobsonUK]

Good introduction, but instead of Keycaster you could have used VS Code's Screencast mode that allows you to show what's being typed more clearly.

[@joelpatrick287]

Thanks for offering this. I learned some new things (cit, for example)! I think it is challenging to try to present because of the mix of the audience.. People have such different levels in vim that it is hard to show things to confirmed vim users without confusing people who are just curious about vim. It would be nice to see another hour or so of Michael Chan's favorite ways of leveraging vim.

[@elementtestdianhua1292]

THANK YOU FOR THIS VIDEO!!!!!! I have been REALLY struggling with trying to use vim in vscode. I am so happy. Really just made my day seeing this!!

[@elementtestdianhua1292]

adding onto that.. would LOVE to see more stuff on vim in vscode. I'm certain I'm not alone

[@Obie.]

Reynald was a great host, and Michael seemed really well versed in vim, but the interruptions for questions really threw off the flow of everything. Definitely should’ve strategized or do a practice run internally to feel it out

[@JayeSpeaks]

@reynaldadolphe I think your compressor mic wasn't on, however a great topic. I'd be interested in any vim related productivity patterns that are unique to VsCode's integration in things like File Explorer, multiple editors, terminal, etc.

[@michaelangellotti5741]

A little too casual & unorganized in your thoughts and teaching outline.

[@slowercuber7767]

BIG thanks for doing this vid. The vi editor (and its successor, vim) is really easy to hate. I loathed vi back in the '80s when my wife and I found it more of a hindrance than a help in doing our school assignments, but in the early 90s, I was assigned to be our group's UNIX (AIX, actually) support guy, so I decided to immerse myself in the hated thing for a month to see if it were possible to at least learn to use it. After a week or two I had found vi to be my new favorite editor. Once the modes are understood and practiced it becomes second nature to retain context and the various commands can quickly get programmed into the same muscle memory you use for typing. Granted, though I've used vi for decades now, I never found it necessary to learn all of it. :w (I recommend that one eschews Z, and I use :wq instead), [esc],~,i,a,r,c,d,y, yy, dd, p, o, (or more commonly, cw), /, !, b, %, n, . (some with f and t qualifiers and associated quantifiers, oc) and ; and in most cases the related capitals (I,A,R,C,D...) (and of course some of the "ed" command-line editor commands (:s/foo/bar/g, :w, etc) are most of the commands I commonly use. So, I'd call much of what you went over today far beyond the simple stuff I used, and I plan on trying to develop a bit of competence with some of these new-fangled syntax aware commands you covered.

[@RetroSmoo]

It's a great extension so you can look at your code without accidentally making changes

[@manjy5927]

always start in Insert mode has unexpected behavior in Python notebooks. It switches from normal mode to insert mode when I navigate to a different cell

[@michalguy]

chan is awesome but the host is just interrupting

[@dadeniman1895]

Hi everyone, is it a way to move from code editor to explorer bar using only keyboard?

[@ajmash9745]

not a bad video, but you could broken the video up, given chapters etc etc, but you didn't capture the keystrokes on screen...

[@code]

Chapters added! Sorry for the delay!

[@AurikSarker]

I like how knowledgeable Chan was, and how clearly comfortable he is with the vim motions. However, I dont think this was the right place to do a vim tutorial - there are literally dozens way better ones online, and this one was WAY too casual.
The reason I clicked in the first place was that I wanted to know how well the vim motions integrate with vs code itself, especially now with all the negative ratings on the extension lately. How does it play with the current keybindings we have on vscode already? How does it work when you're debugging? I feel like a video from the official vscode channel should address these things.

[@MuscleTeamOfficial]

my third attempt at using vscode, only to find out neovim is still better for my needs

[@zeeeeeman]

42:48 Infuriating time to put a question - I can't see exactly what he's typing, and again at 51:30

[@MaxZRider]

No subtitles :( ?

[@tGoldenPhoenix]

35:58

[@fahimemroz9141]

Heresy

[@Undrios]

40:29
(just to comeback to it)

[@yabincheng4171]

Intersting, but not very informative.

[@user-je2ui3zh1m]

I didn't enjoy this at all

[@jpdub45]

This was terrible

[@johnnyvcrow]

Instead of gg top it should have been zz top. 😜🎸