Commit graph

5 commits

Author SHA1 Message Date
Bruno BELANYI 0d1457ee0b [UPDATE][VIM] Remove unused plugins 2020-12-12 14:12:42 +01:00
Bruno BELANYI b610120360 [UPDATE][VIM] Better description for misc mappings 2019-11-05 16:00:42 +01:00
Bruno BELANYI 8b3eb2d05e [ADD][VIM] Mapping to source current buffer 2019-11-05 16:00:42 +01:00
Bruno BELANYI b1db71ddfa [ADD][VIM] Home-row insertion mode escape mappings 2019-11-05 16:00:42 +01:00
Bruno BELANYI a3d8ef9a63 [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-26 00:55:20 +02:00