m-vim_plugins/lightline.vim
1
0
Fork 0
mirror of https://github.com/itchyny/lightline.vim.git synced 2025-11-14 06:23:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

update notes in lightline-spirit

Browse Source
This commit is contained in:
itchyny
2017-05-28 00:41:03 +09:00
parent e0d8d797e2
commit e7636e2028
1 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/lightline.txt
View File

@@ -4,7 +4,7 @@ Version: 0.1
Author: itchyny (https://github.com/itchyny) Author: itchyny (https://github.com/itchyny)
License: MIT License License: MIT License
Repository: https://github.com/itchyny/lightline.vim Repository: https://github.com/itchyny/lightline.vim
Last Change: 2017/05/27 22:59:13. Last Change: 2017/05/28 00:40:46.
CONTENTS *lightline-contents* CONTENTS *lightline-contents*
@@ -40,12 +40,15 @@ SPIRIT *lightline-spirit*
The plugin does not rely on the implementation of other plugins. The plugin does not rely on the implementation of other plugins.
Such plugin crossing settings should be configured by users. Such plugin crossing settings should be configured by users.
You might find this plugin is not so useful by default. This plugin You find this plugin does not integrate with other plugins by default.
does not provide the branch information, which is a very basic This plugin does not provide branch information, which is a basic
component in existing plugins. The reason is that branch component is component in existing statusline plugins. It is a design of
one of plugin crossing settings so users should write the settings lightline.vim that such plugin crossing configuration should be
using the APIs of the both plugins. Hospitality makes a plugin messy. written by users. Once a plugin starts to integrate with some famous
Good APIs keep a plugin clean. plugins, it should be kept updated to follow the changes of the
plugins and should accept integration requests with new plugins.
Instead, lightline.vim is designed very carefully so that users can
easily integrate with other plugins. Good APIs keep a plugin clean.
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
OPTIONS *lightline-option* OPTIONS *lightline-option*