I think this is probably far too nice, but what about
pkill vimHow to Exit Vim
201–210 of 409 posts
Re: How to Exit Vim
#202Earlier quoted context omitted.
It saddens me to say, but this is so familiar. Especially working in a big corporate company where they hire scrum masters who just follow the scrum guide.
Scrum has a built in self destruct method - the retrospective. With a little maneuvering, the team should be able to remove most of the annoying things about scrum by using the retrospective. Obviously you can't go scorched earth and drop all the annoying bits at once. But, if scrum is really being followed (I know this is also part of the problem), the retro should allow the team to change the process over time.
I found that, being a special time set aside specifically for team arguments about how many angels can dance on the head of a pin, the retrospective tends to produce a much more literal version of self-destruction.
I showed up long after they implemented it, so I'm not sure how they got there, but the most well-functioning Scrum team I ever participated in had effectively designated the nominal Scrum Master as a BDFL. The retrospective then became a shorter sort of town hall meeting where everyone aired their opinions, but, since we had a BDFL, we had no need to burn energy on consensus-building. Sadly, things quickly went to hell after she left and the team reverted to a more traditional consensus-oriented approach.
Re: How to Exit Vim
#203The 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"?
Can we also have some sort of a scrumish gathering, ASAP, to declare the correct use of the word "definition", because sometimes it seems we use this word arbitrarily.
Re: How to Exit Vim
#204In the opposing vein, as an Emacs user the best configuration I ever made was to rebind C-x C-c to execute-extended-command instead of kill-emacs. It was way too easy to (even accidentally!) kill emacs with a sweep of a finger. And I probably use a few hundred execute-extended-command calls for each kill-emacs (which I now have to type manually as 'C-x C-c kill-emacs' - no problemo). A similar optimisation was with t…
Emacs is so dynamic and easily configurable, that people can actually rebind a lot of things when their colleague go to the bathroom as a prank. Just open a scratch file, enter some s-expressions, evaluate them, then kill the buffer.
The last time I went to the bathroom as a prank HR had to have another talk with me.
Re: How to Exit Vim
#205Earlier quoted context omitted.
I don't know about vim, but in neovim you're greeted by the following when you launch it the first time: type :help nvim if you are new! type :checkhealth to optimize Nvim type :q to exit type :help for help This joke is pretty outdated :P (But still kind of funny)
You get the same thing in vim, but only when you open it without a file. Chances are, you only do that when you're already a vim user, and most non-users will be confronted with any random program opening a file in vim for them to edit (visudo, git commit, etc.)
git will open pico if you haven't configured an editor. It's annoying.
If you have configured an editor, hopefully you already know how to quit.
Re: How to Exit Vim
#206Earlier quoted context omitted.
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…
You forgot the conversation on the way back from the retrospective about how velocity is a bullshit indicator of actual productivity and we aren't doing agile correctly at this company.
[deleted]
Re: How to Exit Vim
#207Earlier quoted context omitted.
BRS, that old classic Big Red Switch, kills all known operating systems and proc's, dead in their tracks. Me, It's usually :wq, or sometimes :q! or more than likely ZZ - which can be done with shift zz or if you truly want to do it with just one finger, capslock then zz.
:x
Thank you. I swear every time I see a tutorial where someone is using vim they say to save and close with :wq and it drives me nuts.
Re: How to Exit Vim
#208Every time I open vim by accident, I have to restart my computer.
Re: How to Exit Vim
#209One 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.
I disagree completely. When I took CS036 in first year engineering, it was a C++ course that used Visual Studio and while I received a good grade on that course, at the end of it I did not know how to invoke the compiler from the command line. I only knew how to build software from the drop down menu in VS2004 or whatever version it was.
IDEs are a crutch.
Re: How to Exit Vim
#210Earlier quoted context omitted.
This kind of advice confused me early on because I didn't realize the : was part of the command for way too long. For beginners, you might want to spell it out further as: "shift and the : key, then qa, then Enter"
I think that's a great suggestion and probably gets the root of the whole exit vim meme.
I don't have a qa key though