Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
vimagit
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
jreybert
vimagit
Commits
ffd54688
Commit
ffd54688
authored
1 year ago
by
Florent Bouchez Tichadou
Browse files
Options
Downloads
Patches
Plain Diff
Clarified documentation on some bindings.
parent
06afe484
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/vimagit.txt
+7
-3
7 additions, 3 deletions
doc/vimagit.txt
with
7 additions
and
3 deletions
doc/vimagit.txt
+
7
−
3
View file @
ffd54688
...
...
@@ -168,9 +168,9 @@ MAPPINGS *vimagit-mappings*
For each mapping, user can redefine the behavior with its own mapping. Each
variable is described below as *vimagit-g:magit_nameofmapping_mapping*
For example, to redefine the <leader>M mapping
, user should
add this line in
its
|vimrc|:
let g:magit_show_magit_mapping='
m
'
For example, to redefine the <leader>M mapping
to <leader>g,
add this line in
your
|vimrc|:
let g:magit_show_magit_mapping='
<leader>g
'
Mapping update *vimagit-mapping-update*
--------------
...
...
@@ -179,6 +179,10 @@ Since vimagit 1.7, jump mappings have changed:
Jump next hunk : N -> <C-n>
Jump prev hunk : P -> <C-p>
(Previous behaviour can be restored by redefining the following variables:
let g:magit_jump_next_hunk='N'
let g:magit_jump_prev_hunk='P')
Global mappings
---------------
Following mappings are broadly set, and are applied in all vim buffers.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment