It’s useful when vim is being run from a different program or script.
For example, if I run p4 change to create a new Perforce changelist it will open up my editor (which I have set to vim) so that I can enter the CL description and other fields. If I realize I don’t actually actually want to create the CL yet I can use :cq to quit with an error so that p4 knows to abort.
I also have a script I use for diffing a list of file pairs. It runs vim diff on the first pair of files then if I exit with :qa it will move on to the next pair of files. But if I exit with :cq it will just abort and skip all of the remaining file pairs.
According to Stack Overflow, there is also:
I actually knew about ZQ :)
but in what case would you ever need :cq ? I’m curious what’s the idea behind that
Edit: I checked, neither work for obsidian verification, including :cq!
disappointing :c
It’s useful when vim is being run from a different program or script.
For example, if I run
p4 changeto create a new Perforce changelist it will open up my editor (which I have set to vim) so that I can enter the CL description and other fields. If I realize I don’t actually actually want to create the CL yet I can use :cq to quit with an error so thatp4knows to abort.I also have a script I use for diffing a list of file pairs. It runs vim diff on the first pair of files then if I exit with :qa it will move on to the next pair of files. But if I exit with :cq it will just abort and skip all of the remaining file pairs.