First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 94759
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Michael Cummings (RETIRED) <mcummings@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Gustavo M. Gama <gama@vettalabs.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 94759 depends on: Show dependency tree
Bug 94759 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-06-01 11:13 0000
when invoking g-cpan with invalid parameters (i.e., "g-cpan --help"), the
"Usage" message is displayed, as usual. However, in version 0.13-r1, the
definion of the color variables (${white}, ${green}, etc) is done after the
"exit_usage()" method is called, thus causing several warning messages --
complaining about uninitialized variables -- to be printed before the usage
message itself -- and, as a side effect, the usage message has no colors.

Reproducible: Always
Steps to Reproduce:
1. emerge g-cpan
2. g-cpan --help

Actual Results:  
Before the usuage message was displayed, several "warnings" were printed, and
the usage message itself had no colors, as it was supposed to.

Expected Results:  
See above.

The following patch should fix it:

62,67d61
< # Set colors here so we can use them at will anywhere :)
< my $green = color("bold green");
< my $white = color ("bold white");
< my $cyan = color("bold cyan");
< my $reset = color("reset");
< 
81a76,81
> # Set colors here so we can use them at will anywhere :)
> my $green = color("bold green");
> my $white = color ("bold white");
> my $cyan = color("bold cyan");
> my $reset = color("reset");
>

------- Comment #1 From Michael Cummings (RETIRED) 2005-06-01 11:28:56 0000 -------
ack, i had this fixed at one point. expect in 13.01 (so i can avoid the whole 
mess i started with -r1). 

------- Comment #2 From Michael Cummings (RETIRED) 2005-06-01 13:40:04 0000 -------
0.13.01 is in the tree now :) 

First Last Prev Next    No search results available      Search page      Enter new bug