Timeline for Magit always use current branch to create new branch
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 9, 2016 at 0:00 | history | edited | tarsius | CC BY-SA 3.0 |
deleted 111 characters in body
|
| Nov 8, 2016 at 15:09 | comment | added | Wilfred Hughes | Thanks. I've added an example implementation along the lines you suggested. | |
| Dec 30, 2015 at 0:27 | history | edited | tarsius | CC BY-SA 3.0 |
added 9 characters in body
|
| Aug 31, 2015 at 14:20 | vote | accept | Chillar Anand | ||
| Aug 31, 2015 at 14:11 | comment | added | tarsius |
No, but you can copy the definition of magit-branch, look at what happens inside magit-branch-read-args and do something similar inside the interactive of the copy. Then you have to bind that new command in the popup as described here. I.e. my claim that there is a key binding b c RET is not technically correct.
|
|
| Aug 31, 2015 at 12:15 | comment | added | Chillar Anand |
in this context, can i bind c RET to c itself?
|
|
| Aug 31, 2015 at 9:23 | history | answered | tarsius | CC BY-SA 3.0 |