for the three clock options (no clock, a 12-hour clock, or a 24-hour
clock), use the first character of the option as the input to
fix#2266.
This pull request is a reissue of – and supersession of – #2267,
which was pushed on a branch with non-ASCII characters in the name.
Signed-off-by: Lucas Larson <LucasLarson@riseup.net>
Apparently Windows Terminal has a bug. To reproduce:
print -P '\UF0737%K{red} %k'
The expected output:
x_
Here 'x' signifies any glyph of width 1, and '_' signifies a red
block.
The actual output:
x _
Notice the space.
The output of the following two commands is as expected:
print -P '\UFC35%K{red} %k'
print -P '\UFC35x'
`ifconfig`'s formatting doesn't cope well with long interface names. In
these cases it will eat up the whitespace separating the name from the
text "Link" in the output, which makes parsing the output problematic.
e.g. `ifconfig`:
wlp0s20f0u2Link encap:Ethernet HWaddr 00:AA:BB:CC:DD:EE
v.s `ip`:
21: wlp0s20f0u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc \
mq state UP group default qlen 1000
This commit swaps the order of detection inside
`_p9k_prompt_net_iface_async()`, so that `ip` will be preferred.
`ifconfig` is deprecated by distros in favour of `ip`, so this will
often be an incredibly marginal performance boost :)
NOTE: this commit does not address the problem with using `ifconfig`. I
don't understand the zsh regex, so have not touched it.
POWERLEVEL9K_CHRUBY_SHOW_ENGINE_PATTERN defines a pattern that
RUBY_ENGINE should match for it to be shown. Matching is done
with extended_glob.
For example, to show all values of RUBY_ENGINE except "ruby":
POWERLEVEL9K_CHRUBY_SHOW_ENGINE_PATTERN='^ruby'
If POWERLEVEL9K_CHRUBY_SHOW_ENGINE_PATTERN is unset and
POWERLEVEL9K_CHRUBY_SHOW_ENGINE is set to true,
the behavior is the same as if POWERLEVEL9K_CHRUBY_SHOW_ENGINE_PATTERN
was set to *.
Roman Perepelitsa
Lucas Larson
Lazar Jovanovic
NatureLR
Mehyar
Zoltán Reegn
James Winegar
kvanzuijlen
Utkarsh Verma
Leon Satoshi
Clark S. Cox
shwcsmack
Jonathan Sambrook