- 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.
Still needed to push this ebuild to some overlay or main tree; otherwise
it requires more effort to use.
Users need to use
eselect fontconfig enable 10-powerline-symbols.conf
to actually use the fontconfig file (should be added to the docs).
Ebuild itself installs the file, but doesn't enable it.
icanhazip.com has two other domains for fine-tuned IP lookup,
ipv4.icanhazip.com will always return the IPv4 address, and
ipv6.icanhazip.com will always return the IPv6 address (the latter
appears to only work if you actually have an IPv6 address).
Details at http://rackerhacker.com/icanhazip-com-faq/.
Closes#68.
On Linux it appears to work perfectly to just have this font file
present on the system as it automatically chooses fallback fonts if
a glyph isn't present in the current font.
Kim Silkebækken
なつき
ZyX