From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Philipp Zabel <p.zabel@pengutronix.de>, linux-media@vger.kernel.org
Subject: Re: [PATCH v4l-utils 0/2] v4l2-compliance colors
Date: Mon, 8 Apr 2019 13:50:38 -0300 [thread overview]
Message-ID: <20190408135038.6387d595@coco.lan> (raw)
In-Reply-To: <e2a6772f-61a4-8ff8-d815-c71dfd7120e2@xs4all.nl>
Em Mon, 8 Apr 2019 16:46:02 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> On 4/8/19 4:41 PM, Philipp Zabel wrote:
> > On Mon, 2019-04-08 at 12:44 +0200, Hans Verkuil wrote (paraphrased):
> >> On 4/8/19 12:28 PM, Mauro Carvalho Chehab wrote (paraphrased):
> > [...]
> >>>> [I hate colors]
> >>> [I love colors]
> >> I could live with [compromise]
> >
> > Sorry for opening that can of worms :-)
> >
> > How about doing something similar to 'ls':
> >
> > - an environment variable V4L_COLORS which, if not set, defaults to
> > V4L_COLORS="ok=32:warn=1:fail=1;31"
> > - an option --color=always|never|auto, which if not set, defaults to
> > auto (check isatty())
> > - to disable colors by default, set V4L_COLORS to "ok=0:warn=0:fail=0"
> >
> > This would allow to pipe colors into non-terminal stdout like less -R if
> > desired, or quickly disable colors with --color=never.
> > The pattern could be extended to include dvbv5 log levels or fe tool
> > quality levels.
> >
> > Or alternatively, V4L_COLOR=always|never|auto for easier configuration,
> > but with a fixed color scheme?
>
> I think that is easiest. As long as the color scheme works for both black-on-white
> and white-on-black it should be fine.
Instead of V4L2_COLOR, perhaps MEDIA_APPS_COLLOR would be a better name,
as the same env var could be used also for DVB tools.
>
> Regards,
>
> Hans
Thanks,
Mauro
next prev parent reply other threads:[~2019-04-08 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 8:45 [PATCH v4l-utils 0/2] v4l2-compliance colors Philipp Zabel
2019-04-08 8:45 ` [PATCH v4l-utils 1/2] v4l2-compliance: use warn() in warn_once() Philipp Zabel
2019-04-08 8:45 ` [PATCH v4l-utils 2/2] v4l2-compliance: add colors Philipp Zabel
2019-04-08 9:05 ` [PATCH v4l-utils 0/2] v4l2-compliance colors Hans Verkuil
2019-04-08 10:28 ` Mauro Carvalho Chehab
2019-04-08 10:44 ` Hans Verkuil
2019-04-08 14:41 ` Philipp Zabel
2019-04-08 14:46 ` Hans Verkuil
2019-04-08 16:50 ` Mauro Carvalho Chehab [this message]
2019-04-08 16:10 ` Mauro Carvalho Chehab
2019-04-08 16:21 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190408135038.6387d595@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox