Skip to content

Instantly share code, notes, and snippets.

@wilmoore
Created December 11, 2024 17:26
Show Gist options
  • Select an option

  • Save wilmoore/e890b00e13511638d7bcbc0c856aed26 to your computer and use it in GitHub Desktop.

Select an option

Save wilmoore/e890b00e13511638d7bcbc0c856aed26 to your computer and use it in GitHub Desktop.
Personal Brand :: Social Media :: LinkedIn :: Post :: » You Cannot Ignore Vim Even if You've Chosen Visual Studio Code «

Personal Brand :: Social Media :: LinkedIn :: Post :: » You Cannot Ignore Vim Even if You've Chosen Visual Studio Code «

⪼ Made with 💜 by Polyglot.

assistant
reference
  • ...

» You Cannot Ignore Vim Even if You've Chosen Visual Studio Code «

» You Cannot Ignore Vim Even if You've Chosen Visual Studio Code «  

You can't avoid it.  

It's everywhere.  

It's in your `$SHELL`. It's in your `ssh`.  

It's even in your hair 💇🏾‍♀️  

**WHY? WHY? WHY???**  

**WTF G? Q? S? OMG!**  

But, here's the thing...  

You don't have to panic.  

You don't have to throw out the baby with the bathwater.  

You can simply "foreground" Vim.  

Yeah, it’s the `fg` command.  

When you stumble into Vim unexpectedly (we’ve all been there), don’t worry—it’s not a trap you can’t escape from.  

**Foreground it, finish what you're doing, and move on.**  

Vim might seem intimidating, but it's also incredibly versatile. It’s the Swiss Army knife of text editors, hiding in plain sight, ready to save the day—or at least your session.  

💭 Curious about your Vim moments? Got any Vim escape tricks to share? Let me know 👇🏾  

---  

What do you think?

[Comment]



Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment