diff options
| author | Piotr Pawel Stefaniak <pstef@FreeBSD.org> | 2021-08-18 20:47:37 +0000 |
|---|---|---|
| committer | Piotr Pawel Stefaniak <pstef@FreeBSD.org> | 2021-08-19 19:22:16 +0000 |
| commit | ced2dcadccfcff8f7991b3cb5f6f70d6710eadfb (patch) | |
| tree | 984855a813c6fc58f6ef3229aa04bb7bc98b2e2a /crypto | |
| parent | d59c5e023d558161e4f519b88d5209d8bab18bc7 (diff) | |
| download | src-ced2dcadccfcff8f7991b3cb5f6f70d6710eadfb.tar.gz src-ced2dcadccfcff8f7991b3cb5f6f70d6710eadfb.zip | |
ls: prevent no-color build from complaining when COLORTERM is non-empty
As 257886 reports, if ls(1) is built with WITHOUT_LS_COLORS="YES", it
issues a warning whenever COLORTERM is non-empty. The warning is not
useful, so I thought to remove it, but as Ed pointed out, we may want
to have a way to determine whether a particular copy of ls has been
compiled with color support or not.
Therefore move the warnx() call to the getopt loop in
a WITHOUT_LS_COLORS build to fire when the user asks for colored output.
PR: 257886
Reported by: Marko Turk
Reviewed by: kevans
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions