All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hansen <rhansen@bbn.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] test-lib.sh: fix color support when tput needs ~/.terminfo
Date: Wed, 17 Jun 2015 15:55:05 -0400	[thread overview]
Message-ID: <5581D099.7090200@bbn.com> (raw)
In-Reply-To: <20150617194315.GE25304@peff.net>

On 2015-06-17 15:43, Jeff King wrote:
> On Wed, Jun 17, 2015 at 03:06:26PM -0400, Richard Hansen wrote:
>> +	say_color_error=$(tput bold; tput setaf 1) # bold red
>> +	say_color_skip=$(tput setaf 4) # blue
>> +	say_color_warn=$(tput setaf 3) # brown/yellow
>> +	say_color_pass=$(tput setaf 2) # green
>> +	say_color_info=$(tput setaf 6) # cyan
>> +	say_color_sgr0=$(tput sgr0)
>> [...]
>> +		error|skip|warn|pass|info)
>> +			eval "say_color_color=\$say_color_$1";;
>>  		*)
>>  			test -n "$quiet" && return;;
> 
> I think you could dispense with this case statement entirely and do:
> 
>   eval "say_color_color=\$say_color_$1"
>   if test -z "$say_color_color"; then
>           test -n "$quiet" && return
>   fi
> 
> I guess that is making the assumption that all colors have non-zero
> sizes, but that seems reasonable.

We could test if the variable is set first (test -n "${foo+set}"), at
the cost of a bit more complexity.

> I do not mind it so much as you have
> it, but it does mean adding a new field needs to update two spots.

I also don't like the duplicate list of color types, and I considered
doing something similar to what you suggested, but I decided against it.
 I'm a bit worried about bizarre syntax errors or code execution if
say_color() is used improperly.  ('eval' with uncontrolled variables
makes me nervous.)

Thanks for reviewing,
Richard

  reply	other threads:[~2015-06-17 19:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 19:06 [PATCH 0/2] redo fix for test-lib.sh color support Richard Hansen
2015-06-17 19:06 ` [PATCH 1/2] Revert "test-lib.sh: do tests for color support after changing HOME" Richard Hansen
2015-06-17 19:06 ` [PATCH 2/2] test-lib.sh: fix color support when tput needs ~/.terminfo Richard Hansen
2015-06-17 19:43   ` Jeff King
2015-06-17 19:55     ` Richard Hansen [this message]
2015-06-17 20:15       ` Junio C Hamano
2015-06-17 21:11         ` [PATCH v2 0/2] redo fix for test-lib.sh color support Richard Hansen
2015-06-17 21:11           ` [PATCH v2 1/2] Revert "test-lib.sh: do tests for color support after changing HOME" Richard Hansen
2015-06-17 21:11           ` [PATCH v2 2/2] test-lib.sh: fix color support when tput needs ~/.terminfo Richard Hansen
2015-06-17 22:13             ` Jeff King
2015-06-17 22:23               ` Junio C Hamano
2015-06-17 22:26                 ` Jeff King
2015-06-17 20:25       ` [PATCH " Jeff King

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=5581D099.7090200@bbn.com \
    --to=rhansen@bbn.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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 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.