From: "Wiles, Keith" <keith.wiles@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>, Arnon Warshavsky <arnon@qwilt.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PKTGEN] additional terminal IO question
Date: Sun, 24 Jan 2016 19:46:58 +0000 [thread overview]
Message-ID: <650FC079-06CB-4B1D-9C3D-2E4B2E92F216@intel.com> (raw)
In-Reply-To: <20160123024826.GB25867@mhcomputing.net>
On 1/22/16, 9:48 PM, "Matthew Hall" <mhall@mhcomputing.net> wrote:
>On Thu, Jan 21, 2016 at 05:35:00PM +0200, Arnon Warshavsky wrote:
>> Keith,
>> For the record, on my end (can only speak for myself) this is not a real
>> problem.
>> I work around it by using a different theme and live with it happily ever
>> after.
>> I just provided the input since I encountered it.
>>
>> /Arnon
>
>For me, breaking stuff with a black background to gain questionably useful
>colors and/or themes seems like more overhead for cognition of the code for
>not much benefit.
>
>This is going to break the tool people who use a Linux standard framebuffer
>with no X also, isn't it?
You can disable the themes or colors by not including the -T option on the command line.
The colors and terminal control are all ASCII codes, which most terminals will support even on a standard serial console.
>
>Matthew.
>
Regards,
Keith
next prev parent reply other threads:[~2016-01-24 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:53 Matthew Hall
2016-01-21 6:00 ` Arnon Warshavsky
2016-01-21 6:02 ` Matthew Hall
2016-01-21 14:55 ` Wiles, Keith
2016-01-21 15:04 ` Arnon Warshavsky
2016-01-21 15:27 ` Wiles, Keith
2016-01-21 15:35 ` Arnon Warshavsky
2016-01-23 2:48 ` Matthew Hall
2016-01-24 19:46 ` Wiles, Keith [this message]
2016-01-25 9:20 ` Andriy Berestovskyy
2016-01-25 19:10 ` Matthew Hall
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=650FC079-06CB-4B1D-9C3D-2E4B2E92F216@intel.com \
--to=keith.wiles@intel.com \
--cc=arnon@qwilt.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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;
as well as URLs for NNTP newsgroup(s).