new option: g:startify_custom_indices
People can now choose to create their own index mapping instead of having the default behaviour of increasing numbers. Closes #17.
This commit is contained in:
parent
7ab3ca8565
commit
4711a54cf5
3 changed files with 49 additions and 8 deletions
|
@ -144,6 +144,34 @@ name contained in this list.
|
|||
Example: let g:startify_skiplist_server = [ 'GVIM' ]
|
||||
|
||||
|
||||
============-
|
||||
|
||||
let g:startify_custom_indices = []
|
||||
|
||||
Use any list of strings as custom indices instead of increasing numbers. If
|
||||
there are more paths to fill in the startify buffer than actual items in the
|
||||
custom list, the rest will be filled up using the default numbering scheme
|
||||
starting from 0.
|
||||
|
||||
NOTE: There is no sanitizing going on, so you should know what you do!
|
||||
|
||||
E.g. you don't want to use duplicates. Same for 'e', 'i', 'q'. Actually you
|
||||
can use them, but they would be overwritten by mappings for creating the empty
|
||||
buffer and quitting. You may want to keep 'j' and 'k', too.
|
||||
|
||||
Example: let g:startify_custom_indices = ['a','s','d','f']
|
||||
|
||||
This would result in:
|
||||
|
||||
[a] /last/recently/used/file1
|
||||
[s] /last/recently/used/file2
|
||||
[d] /last/recently/used/file3
|
||||
[f] /last/recently/used/file4
|
||||
[0] /last/recently/used/file5
|
||||
[1] /last/recently/used/file6
|
||||
etc.
|
||||
|
||||
|
||||
============-
|
||||
|
||||
let g:startify_unlisted_buffer = 1
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue