Age | Commit message (Collapse) | Author |
|
|
|
Use a prefix argument instead of having separate commands for
switching projects.
|
|
|
|
|
|
Should have replaced in bf1bacdf8fd3137172588c17a58336ecfd0ba81f.
|
|
Magit commit 1ff241b719 removed magit-get-top-dir.
|
|
Removed in Magit 3026b56182c.
|
|
|
|
|
|
|
|
https://github.com/magit/magit/issues/1677
|
|
|
|
|
|
|
|
|
|
A similar action was added to Magit in
a471cfb94c762a714570a86a75004770fb6214c3.
|
|
|
|
|
|
|
|
|
|
A revision doesn't make sense because the '--all' flag is being
passed.
|
|
- Use letter pairs that are rare in both directions. For really
common commands, try to keep my fingers on home row.
- Remove some key chords for less frequent commands. For Projectile,
just bind switching projects and the commander because most other
things are available with one more key from the commander.
My strategy for key chord bindings was to lead with ',' or ';' and
then follow with any letter. The idea was that, with the languages and
coding conventions I was using at the time, when I inserted a comma or
semicolon, they were usually followed by a non-letter (typically a
space or a new line). But, this is actually not a good way to go
about this because Key chord mode accepts the two-letter combination
in either order. In practice, I didn't end up unintentionally calling
a command too often, but it did happen enough to be slightly annoying.
John Cook recently posted a table [1] of bigram frequencies, which is
a good starting point for updating my key chords.
[1]: http://www.johndcook.com/blog/2015/02/01/rare-bigrams/
|
|
Magit commit a44ed1b9c3b0ffa09b988cb8305da0105e4702ea
|
|
|
|
- Add pages and more headings for large files.
- Try to use consistent order for file (or page) structure.
* Loading
* Settings
* Hooks
* Any mode activation or function calls
* My functions
* Key bindings
|
|
|
|
|
|
|
|
Bind this version to SPC. This is more consistent with behavior in the
log buffer, where RET shows the commit and switches to that buffer and
SPC just displays the commit.
However, the SPC variants still differ in their scrolling behavior. In
the log buffer, SPC (magit-diff-show-or-scroll-up) will scroll if the
buffer is already displayed, but km/git-rebase-show-commit doesn't
support this. While it'd be nice to use magit-diff-show-or-scroll-up
directly, this isn't easy to do because magit-diff-show-or-scroll-up
doesn't take a revision argument (it pulls it directly from the magit
section).
|
|
|
|
|
|
Magit commit 23f4f8dd3abe4dd7ee57d8edd62421f1f2c6daea introduced
magit-status-internal.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Magit now contains git-commit-mode.el, git-rebase-model.el, and
with-editor.el from the git-modes repo.
Magit commit 6e601926278a833baed7a9f44f7f6a360be203da
|
|
|
|
Magit commit 893e2fea941335f1f428c2e1f996e42822b0fe59
|
|
Magit has removed magit-log-dwim [1] and changed the arguments to
magit-log-read-args [2].
[1] e0979bb6bd22a9ce5009a7cdf458034e52817da3
[2] 5737de048843bbad83f16ea13f57d69cdbe6971e
|
|
This is slow for repos that contain lots of tags.
|
|
|
|
|
|
|
|
|
|
As of Magit c268e7f, backups won't occur if the mode is disabled.
|
|
|