The tmux theme has been updated and now matches the other themes much
better. It may still look a little boring and segment cropping isn't
enabled, but it's a good starting point. It colors the weather segment
differently based on the current weather and temperature, and some other
segment colors have been tweaked.
To enable the theme, add the following to your tmux.conf:
source '/full/path/to/powerline/bindings/tmux/powerline.conf'
Closes#51.
This only displays the left part of the prompt. It requires the
left-only theme to be able to display all segments.
The script must be sourced with an absolute path for now:
. /path/to/powerline/bindings/bash/prompt.sh
Closes#90.
This script sets a couple of environment variables in tmux if it's
running, and provides the last exit code and last pipe status to
powerline-prompt. It also traps SIGWINCH and sets the window width as an
env variable in tmux. The default prompt has been split in two and the
git branch is moved to RPS1.
The script must be sourced with an absolute path for now:
. /path/to/powerline/bindings/zsh/prompt.zsh
Statusline cropping has not been implemented in powerline-tmux yet.
Closes#82.
Closes#83.
Refs #90.
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
Kim Silkebækken
ZyX
なつき