Why is :wq so hard?
How to Exit Vim
191–200 of 409 posts
Re: How to Exit Vim
#192The 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…
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.
Re: How to Exit Vim
#193Earlier quoted context omitted.
> `ddkP` is probably the most advanced command I know Maybe I'm not thinking straight because of the sickness, but I think `ddp` from the line above does the same thing with one fewer keystroke.
`P` pastes to the line above .
That’s why the poster above suggested doing it from the line above. kddp still saves you from the burden of pressing the shift key.
(Works if register contents after the operation do not matter to you; I don’t think the OP knows or cares what registers are)
Re: How to Exit Vim
#194It's amazing to think how far we've come since June 2018 where the record was just shy of three minutes ( https://www.youtube.com/watch?v=TLbfqZBL8t8 ). These new strategies could allow experienced speedrunners to exit vim in times of 10 seconds (or perhaps less!?). I'm excited to see how this progresses, the vim speedrun community is vibrant and creative and I've no doubt we'll see a sub 5-second run within my lifet…
Must be GDQ season again.
Re: How to Exit Vim
#195Earlier quoted context omitted.
'screen' uses C-a as a prefix shortcut so developers of 'tmux' decided to use the next available key to avoid clash.
I don't understand the logic there. In what non-contrived scenario would you run both simultaneously, such that they would conflict? C-a does annoyingly conflict with readline's "move to start of line", though.
1. Outer tmux on local/primary machine, for your usual daily use-case (i.e. managing multiple terminal sessions).
2. In outer tmux, ssh to some other machine you need to administrate.
3. screen because you need multiple terminal sessions on that machine, or need detachability/reconnectability for some long-running process.
Re: How to Exit Vim
#196Earlier 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…
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.
Re: How to Exit Vim
#197some people have way too much free time.
Re: How to Exit Vim
#198Earlier 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.
This obviously only works when your scrum master is willing to take feedback on scrum processes. Which, with most scrum masters is not the case, you’re essentially telling them they’re doing a bad job, and it usually hurts their ego.
Re: How to Exit Vim
#199`ZQ` in normal mode exists VIM with no trouble. 2 keystrokes compared to `:q`
Re: How to Exit Vim
#200It's amazing to think how far we've come since June 2018 where the record was just shy of three minutes ( https://www.youtube.com/watch?v=TLbfqZBL8t8 ). These new strategies could allow experienced speedrunners to exit vim in times of 10 seconds (or perhaps less!?). I'm excited to see how this progresses, the vim speedrun community is vibrant and creative and I've no doubt we'll see a sub 5-second run within my lifet…
There is a much faster way, but first you need to build up speed for 12 hours.