Welcome to the best online casino: win your million in slots
Play the spins for a chance to win one of the BitStarz Jackpots!
Play now
You can enjoy your favorite slot games with us
Welcome to the best online casino: win your million in slots
Play the spins for a chance to win one of the BitStarz Jackpots!
Play now
In his excellent introduction to Magit, Mickey Petersen does a great job of explaining basics of Magit workflowIn his excellent introduction to Magit, Mickey Petersen does a great job of explaining basics of Magit workflow. The entry point to Magit, which is magit-status, is not bound to any key by default, so after switching to Git and Magit, I bound it to (previously undefined) C-x g
That’s right – and it’s a pityBut when I was reading Mickey’s article, one thing struck me. That’s right – and it’s a pity
The entry point to Magit, which is magit-status, is not bound to any key by default, so after switching to Git and Magit, I bound it to (previously undefined) C-x gI don’t want to rebind it to magit-status, since I have a lot of Hg repos I still use, and I need vc-next-action for them, I put this in my init. In his excellent introduction to Magit, Mickey Petersen does a great job of explaining basics of Magit workflow
el:Of course, I lose the possibility of using magit-status with prefix arguments with this simple setup, but it’s not a problem for me; for switching between projects, I’m fine with C-x C-f (and Ido), and for setting up a new repo, M-! git init is good enough for meThe entry point to Magit, which is magit-status, is not bound to any key by default, so after switching to Git and Magit, I bound it to (previously undefined) C-x g. el:Of course, I lose the possibility of using magit-status with prefix arguments with this simple setup, but it’s not a problem for me; for switching between projects, I’m fine with C-x C-f (and Ido), and for setting up a new repo, M-! git init is good enough for me