161–170 of 409 posts
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.
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.
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.
If exiting vim is too easy, try the advanced level: exiting "vim -y".
That should do it. ;)
Ctrl-o moves from INSERT mode to COMMAND mode for one command and so it still works in "easy" mode. I notice that "easy" mode was one of the things that the Nvim guys removed.
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…
The whole thing is followed up with a two hour retrospective where we pat ourselves on the back for increasing velocity (due to assigning story points to closing vim).
Bonus points if you then are asked to map that back to actual hours so we can estimate completely unrelated future tasks while simultaneously remembering that we don't estimate in hours.
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...
It's not a bug, it's a feature.
ED(1) Unix Programmer's Manual
NAME
ed - text editor
SYNOPSIS
ed [ - ] [ -x ] [ name ]
DESCRIPTION
Ed is the standard text editor.
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…
13. Ask the team what we can do to make sure we don't have to miss the deadline
Tell a room full of comp100 students to save and exit vim :)
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…
There is a step somewhere in there where we waste 30 minutes playing "agile poker" and arguing about the number of story points required to close vim. The whole thing is followed up with a two hour retrospective where we pat ourselves on the back for increasing velocity (due to assigning story points to closing vim). Bonus points if you then are asked to map that back to actual hours so we can estimate completely unr…