From: Pierre Habouzit <madcoder@debian.org>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add some fancy colors in the test library when terminal supports it.
Date: Mon, 22 Oct 2007 14:11:06 +0200 [thread overview]
Message-ID: <20071022121106.GA7151@artemis.corp> (raw)
In-Reply-To: <471C8B02.6080202@viscovery.net>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On Mon, Oct 22, 2007 at 11:35:30AM +0000, Johannes Sixt wrote:
> Pierre Habouzit schrieb:
> >On Mon, Oct 22, 2007 at 08:53:36AM +0000, Johannes Sixt wrote:
> >>Pierre Habouzit schrieb:
> >>>+say_color () {
> >>>+ [ "$nocolor" = 0 ] && [ "$1" != '-1' ] && tput setaf "$1"
> >>>+ shift
> >>>+ echo "* $*"
> >>>+ tput op
> >>>+}
> >>What if tput is not available, like on Windows? How about this (at the
> >>end of the file, so it can obey --no-color):
> > I answered to it already in my first mail: if tput isn't available,
> >the command fails, and $? is non 0. and nocolor is set. Or color isn't
> >set to 't' for your proposal.
>
> I was too terse, sorry. I wanted to point out that if tput is not
> available, the second invocation will leave "tput: command not found"
> behind on stderr. Therefore, I proposed to make the definition of
> say_color() different depending on whether $color is set or not. Then you
> don't need to test for $color twice inside the function.
Right we can do that. I'll try to rework the patch. and no it
shouldn't leave tput: command not found as I 2>/dev/null and I think the
shell doesn't print that in that case. At least my zsh doesn't.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-22 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 8:13 [PATCH] Add some fancy colors in the test library when terminal supports it Pierre Habouzit
2007-10-22 8:53 ` Johannes Sixt
2007-10-22 11:24 ` Pierre Habouzit
2007-10-22 11:35 ` Johannes Sixt
2007-10-22 12:11 ` Pierre Habouzit [this message]
2007-10-22 12:18 ` Johannes Sixt
2007-10-22 13:45 ` Pierre Habouzit
2007-10-23 4:08 ` Christian Couder
2007-10-23 6:37 ` Johannes Sixt
2007-10-23 8:13 ` Pierre Habouzit
-- strict thread matches above, loose matches on Subject: below --
2007-10-24 20:03 Small enhancements of the test-lib.sh Pierre Habouzit
[not found] ` <1193256219-24222-2-git-send-email-madcoder@debian.org>
2007-10-24 20:28 ` [PATCH] Add some fancy colors in the test library when terminal supports it Pierre Habouzit
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=20071022121106.GA7151@artemis.corp \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=spearce@spearce.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.