Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to Exit Vim

github.com

Post reply on HN
Print view View original

181–190 of 409 posts

Re: How to Exit Vim

#181

Post by fourthark »

Lio wrote: post #148
talles wrote: post #135

Jokes aside, shouldn't the page start with actually teaching how to quit vim? The page is considerably popular to show up on a Google search. I imagine the frustration of a beginner actually trying the first examples and not getting the joke immediately.

Yeah, I mean if you really wanted to help people exit Vim you'd trap Ctrl-c in command mode and print the instructions at the bottom of the screen. Something along the lines of "Type :qa and press to exit Vim" would probably do it...

Yes, the version on my machine prints

    Type  :qa!  and press  to abandon all changes and exit Vim

Re: How to Exit Vim

#182

Post by phkahler »

screye wrote: post #161
talles wrote: post #135

Jokes aside, shouldn't the page start with actually teaching how to quit vim? The page is considerably popular to show up on a Google search. I imagine the frustration of a beginner actually trying the first examples and not getting the joke immediately.

Nope. The best thing that can happen to a beginner is they continue being frustrated with vim, quit it before they get in too deep, and just use shitty idees like the rest of us trash.

My first go at vim was an accident. I was using git and ended up there. I later tried to change the editor invoked by git to something else, but have concluded that was dumb and the only real option is to learn vim. It's still on my todo list. As is the actual OSS work I want to contribute after climbing this hill. It should not be this way.

Re: How to Exit Vim

#183

Post by ivanovb »

bob33212 wrote: post #168
franze wrote: post #145

The Scrum manager way 1. Call in a meeting, early in the morning 2. Tell everybody what a good job they are doing. 3. Tell everybody that there is still a lot to do. 4. Tell everybody that "we" can do it. 5. Remind them of the importance of team work. 6. Go through the tickets. 7. Tell the project manager that a ticket for closing Vim is missing. 8. Write a ticket called "As a user I want to exit Vim!" on your own. 8…

10.5 create a deadline 13. Ask the team what we can do to make sure we don't have to miss the deadline

14. Move the deadline 2 months in the future.

Re: How to Exit Vim

#185

Post by ezzzzz »

ramraj07 wrote: post #93
yodsanklai wrote: post #65

Earlier quoted context omitted.

> And of course I'd have to dive deep into the ecosystem in order to get the same benefits that my main editor provides out of the box, To me, vim shines as a modal editor , not an IDE. I use it for two purpose: 1. quick editing configuration files, or single file scripts 2. an editing mode in an IDE (mostly VSCode) The main benefit of vim is to save you from using the mouse or the touch pad. I touch type, my indexes…

My hypothesis is that vim style work (without moving a wrist even a bit) is the reason people get carpel tunnel. I anecdotally see far fewer (none?) People who don't do vim/emacs getting these injuries. Makes sense as well right? Just like "take a walk and don't sit in the same place" but for your fingers

I don't know about carpel tunnel, but the reason I became interested in Vim/Emacs was due to RSI caused by using a mouse. This was my first job, doing shudders Java-EE (7) web development (no live re-loading, tons of clicking in IDE, manually reloading web-page etc, crappy windows touch-pad etc).

Started learning Rails, drank the Kool-Aid, switched to VIM. I don't use VIM for development at my day-job, mostly just key-bindings in Intellij/VS Code, however, the amount of time saved has been worth the effort, and no RSI (also thankfully am able to use the fantastic track-pad on mac and a trackball for anything else).

Lately I've been feeling the pull to learn Emacs after learning about ORG-Mode and the extensibility of the software... unfortunately, the time investment here is likely to have no real benefit in my (current) work as a Java dev. Sigh, time to browse the who's hiring thread.

Re: How to Exit Vim

#186

Post by [deleted] »

ChrisRR wrote: post #157
joeraut wrote: post #122

One of my Computer Science lecturers had a rule: use Vim for all development for his class whilst on campus, and if caught using any other editor/IDE – or committing any artifacts showing evidence of such – we would lose several percentage points from our final mark for his class. Harsh? Perhaps. But I can’t thank that lecturer enough for that rule. He converted a mostly IDE-wielding class into one that actually appr…

That's stupid and elitist. There's no reason to force students to go against IDEs that they're already used to, but also the general method of navigating around a computer which they're probably used to from MS Word etc.

[deleted]

Re: How to Exit Vim

#187

Post by RawToluene »

phkahler wrote: post #182
screye wrote: post #161

Earlier quoted context omitted.

Nope. The best thing that can happen to a beginner is they continue being frustrated with vim, quit it before they get in too deep, and just use shitty idees like the rest of us trash.

My first go at vim was an accident. I was using git and ended up there. I later tried to change the editor invoked by git to something else, but have concluded that was dumb and the only real option is to learn vim. It's still on my todo list. As is the actual OSS work I want to contribute after climbing this hill. It should not be this way.

You don't ever tick that item on the todo list. Learning vim is a never-ending path to wisdom.

Re: How to Exit Vim

#188

Post by SamuelAdams »

rezeroed wrote: post #178
franze wrote: post #145

The Scrum manager way 1. Call in a meeting, early in the morning 2. Tell everybody what a good job they are doing. 3. Tell everybody that there is still a lot to do. 4. Tell everybody that "we" can do it. 5. Remind them of the importance of team work. 6. Go through the tickets. 7. Tell the project manager that a ticket for closing Vim is missing. 8. Write a ticket called "As a user I want to exit Vim!" on your own. 8…

Don't you need a definition of "done"?

User is able to exit VIM by throwing their laptop out the window and vacationing to Cancun.

Re: How to Exit Vim

#189

Post by Kye »

numlock86 wrote: post #115

I was on a remote system and remember I couldn't exit vi. What did I do? Well, I opened a second ssh session, looked up the process id with ps and killed it. This is so many decades ago ... like the very beginning of my curiosity when it comes to IT basically. Thinking back to it, I wonder how I was able to use ssh and tools like grep, ps and kill but did not know how to operate basic vi ...

I did similar with early desktop Linux. vim opened up in one of the ttys, and I couldn't figure out how to close it, so I hopped to another tty and killed it.

Re: How to Exit Vim

#190

Post by kerkeslager »

As a senior dev, I wanted to pat myself on the back and say

   :q
But then I realized that the senior dev way is more like:

1. Look it up on Stack Overflow.

2. Send the Stack Oveflow to the intern and tell intern to do it.

3. Reject the PR because it lacks unit tests.

4. Reject the PR because it didn't account for an obscure case that product usually is concerned about.

5. Reject the PR because it there's a simpler way to do it.

6. Pair program with the intern because they're having trouble.

7. Realize that tests are a bit overkill, the obscure case can't happen, and the complexity is because of trying to make it testable and handling the obscure case.

8. Merge a PR that looks suspiciously like what the intern originally submitted.

9. When QA rejects, send back to QA asking for steps to reproduce (har har).

10. When QA sends back steps to reproduce, send back saying you can't reproduce (har har).

11. Sit with QA and see that the bug exists, because they doing something you didn't think of.

12. Fix the bug, merge the code.

13. When the manager asks you to, create the story in Pivotal and push it through all the states (everything so far happened in Slack).

14. Years later, come across the same problem at a different company, and notice someone `:q` in one of the side comments on Stack Overflow, which was there the last time you looked, you didn't notice it.

Post reply on HN