diff options
author | Thomas Haller <thaller@redhat.com> | 2018-06-21 18:00:31 +0200 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2018-06-24 14:19:06 +0200 |
commit | 4cb078f94442e1e3d4b4275bf579bac5e04d2c70 (patch) | |
tree | 82cfd2b5740625c27435027fa7748be2127bf6b2 /clients/tests/test-client.check-on-disk/test_003-199.expected | |
parent | 209af9fadee3d5734ce5c5a4e717d7c5589eec69 (diff) | |
download | NetworkManager-4cb078f94442e1e3d4b4275bf579bac5e04d2c70.tar.gz |
cli: rework check-colors to first evaluate enabled/disabled
With --color=auto, coloring is enabled based on the .enable/.disable
termcolors files.
Likewise, when we enable coloring, we parse the color palette from the
.schem termcolors files.
The termcolors files are searched by finding the best match depending
on the terminal and application name. Note, that if we find a matching
file like "nmcli@xterm.enable" we still allow loading the palette from
a less specific file like "nmcli.schem" and vice versa. That was already
done before.
Previously, the search was done by calling several layers of functions, and having
in/out arguments "color_option" and "p_palette_buffer". in/out paramters
here seems confusing to me, as they are state that gets modified and carried
along.
Instead, rework the functions to clearly separate between input
and output arguments.
Also, in the auto-case, check_colors() now first determines whether
coloring is enabled, before even starting loading the palette.
This avoids loading the palette until we are sure that we need it.
Diffstat (limited to 'clients/tests/test-client.check-on-disk/test_003-199.expected')
0 files changed, 0 insertions, 0 deletions