This requires a couple of minor changes to custom segments. The segment
`highlight` key has been renamed to `highlight_group`, and segment
functions must return a list of segments dicts instead of just a dict.
Closes#88.
Powerline now detects the Python version and verifies that the user has
Python 3.3 before enabling Python 3 support. To enable Python
3 support, use `python3` to execute source_plugin() in your vimrc
instead of `python2`.
Support for unicode literals was reintroduced in Python 3.3 which makes
supporting both Python 2 and Python 3 much easier, so this will be the
minimum supported Python 3 version.
Closes#8.
psutil is used if available, and the function falls back to reading
/proc/uptime if not. According to the psutil docs this should work
across more platforms.
- It was impossible to configure visual block and select block mode strings:
JSON strings can contain neither raw control characters nor escape sequences
for them
- It was impossible to override only some of the strings:
missing key generates KeyError exception, not IndexError
- Added notes about where common and extension-specific configuration is located
- Added common.paths config.json option description
- Fixed user-defined segments location found in segments section
- Fixed Themes/segments/module reference text
Here are two fixes:
- defaultdict makes it not throw KeyErrors.
- Replacing (False, False) with False makes it not throw vim.error (no color
ctermbg=False)
This should ideally be renamed to something else since it's not strictly
an extension. A better module naming scheme could be something like:
powerline.segments.ext.{extension}
powerline.segments.common
This would move all segments out of their respective extension
directory, and might be a bit confusing. The ext directories may also
need some changes to make this work properly.
Kim Silkebækken
なつき
ZyX