ambroisie/dot-files
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
dot-files/vim/.vim/after/plugin/mappings/fzf.vim

39 lines
951 B
VimL
Raw Normal View History

[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" Only git-tracked files, Vim needs to be in a Git repository
nnoremap <Leader>fg :GFiles<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" All files
nnoremap <Leader>ff :Files<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" Currently open buffers
nnoremap <Leader>fb :Buffers<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" Buffer history
nnoremap <Leader>fh :History<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" Tags in buffer
nnoremap <Leader>ft :BTags<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" Tags in all project files
nnoremap <Leader>fT :Tags<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" Snippets for the current fileytpe (using Ultisnips)
nnoremap <Leader>fs :Snippets<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" All available commands
nnoremap <Leader>f: :Commands<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" All commits (using fugitive)
nnoremap <Leader>fc :Commits<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
[UPDATE][VIM] Move mappings to different files Because a lot of my mappings use the <Leader> key, this is the only file that *must* be loaded before all the others, otherwise the value of leader when the script is read will be erroneous. I also tried to use `git write-tree` and `git commit-tree` to emulate a manual octopus merge to preserve the line history for each file. But honestly that gave a graph that was too ugly for a history that really did not need that amount of accountability. However it is a fun exercise, and I recommend to everyone to try it at least once. See Raymond Chen's blog `The Old New Thing`, with the post titled `How to split out pieces of a file while preserving git line history: The hard way with commit-tree`, for an explanation.
2019-10-25 23:59:51 +02:00
" All commits for the current buffer (using fugitive)
nnoremap <Leader>fC :BCommits<CR>
[ADD][VIM] Mapping search using fzf
2019-11-04 11:56:18 +01:00
" Select normal mode mapping by searching for its name
nmap <Leader><Tab> <Plug>(fzf-maps-n)
" Select visual mode mapping by searching for its name
xmap <Leader><Tab> <Plug>(fzf-maps-x)
" Select operator pending mode mapping by searching for its name
omap <Leader><Tab> <Plug>(fzf-maps-o)
Reference in a new issue Copy permalink