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

23 lines
643 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
" Yank until the end of line with Y, to be more consistent with D and C
nnoremap Y y$
[UPDATE][VIM] Better description for misc mappings
2019-11-04 18:03:11 +01:00
" Edit my vimrc in the current buffer
[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
nnoremap <Leader>ev :edit $MYVIMRC<CR>
[UPDATE][VIM] Better description for misc mappings
2019-11-04 18:03:11 +01:00
" Source my vimrc
[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
nnoremap <Leader>es :source $MYVIMRC<CR>
[UPDATE][VIM] Better description for misc mappings
2019-11-04 18:03:11 +01:00
" Source the current buffer
[ADD][VIM] Mapping to source current buffer
2019-11-04 17:54:31 +01:00
nnoremap <Leader>et :source %<CR>
[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
[ADD][VIM] Home-row insertion mode escape mappings
2019-11-04 17:53:57 +01:00
" Easier escape from insert mode
inoremap jkj <Esc>
inoremap kjk <Esc>
[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
" Run make silently, then skip the 'Press ENTER to continue'
noremap <Leader>m :silent! :make! \| :redraw!<CR>
" Remove search-highlighting
noremap <Leader><Leader> :nohls<CR>
" Explicit map for vim-cheat40 which seems to fail because of my <Nop> map
map <Leader>? :<C-u>Cheat40<CR>
Reference in a new issue Copy permalink