Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Changing paradigm of creating mappings
* Maps are being stored as a hash to allow fine-grain control over which maps to enable/disable * Maps are not global by default. All code related to buffer-specific mappings has been removed * Added new movement - Jump to marker of any type * Added new setting - g:SignatureEnabledAtStartup
- Loading branch information
Showing
5 changed files
with
350 additions
and
327 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Original file line | Diff line number | Diff line change |
---|---|---|---|
@@ -1 +1,2 @@ | |||
tags | tags | ||
.tags |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Original file line | Diff line number | Diff line change |
---|---|---|---|
@@ -1,3 +1,18 @@ | |||
### NOTE | |||
vim-signature has undergone some changes recently, the biggest of which are | |||
* Maps are specified using a hash. My hope is that this will allow finer control over which maps to enable/disable and eliminate all the default mapping variables | |||
* Maps are now global by default. It was cumbersome to think of a good way to implement buffer-specific maps and support it. The previous method was clunky at best ( see the number of issues related to maps ) and caused more trouble than they were worth. So I decided to get rid of it. | |||
|
|||
Q. So how does this affect me? | |||
A. Well, if you were using the default maps then I've tried to change things as little as possible (at least in the frontend) and I hope it shouldn't. But if you were using custom maps, then you'll have to set it up again using the new hash method. | |||
|
|||
Q. Are there any changes not related to maps? | |||
A. Why yes, there is now a new method to jump to marker of any type. This is mapped to `]=` and `[=` by default. | |||
There is also a new setting to control if the signs should be shown by default at startup. Check out g:SignatureEnabledAtStartup | |||
|
|||
For those who wish to continue the older version, I've created a new branch `stable_4104e0bb6c` | |||
|
|||
|
|||
# vim-signature | # vim-signature | ||
vim-signature is a plugin to place, toggle and display marks. | vim-signature is a plugin to place, toggle and display marks. | ||
|
|
||
|
@@ -47,6 +62,8 @@ Once that's done, out of the box, the followings mappings are defined | ||
m<S-[0-9]> : Remove all markers of the same type | m<S-[0-9]> : Remove all markers of the same type | ||
]- : Jump to next line having same marker | ]- : Jump to next line having same marker | ||
[- : Jump to prev line having same marker | [- : Jump to prev line having same marker | ||
]= : Jump to next line having same marker | |||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
kshenoy
Author
Owner
|
|||
[= : Jump to prev line having same marker | |||
m<BackSpace> : Remove all markers | m<BackSpace> : Remove all markers | ||
```` | ```` | ||
|
|
||
|
@@ -71,5 +88,4 @@ For more details on customization refer the help | ||
|
|
||
|
|
||
## ToDo: | ## ToDo: | ||
* Add support for non-Alphabetical marks | |||
* Tie the Signature functions to vim commands that affect mark placement | * Tie the Signature functions to vim commands that affect mark placement |
Oops, something went wrong.
This is the same description as for
]-