blob: 8fecff6ef016e4b82903f284caa0bb1f974995fa (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
package Carp::Always::Color;
use strict;
use warnings;
# ABSTRACT: Carp::Always, but with color
BEGIN {
if (-t *STDERR) {
require Carp::Always::Color::Term;
}
else {
require Carp::Always::Color::HTML;
}
}
=head1 SYNOPSIS
use Carp::Always::Color;
or
perl -MCarp::Always::Color -e'sub foo { die "foo" } foo()'
=head1 DESCRIPTION
Stack traces are hard to read when the messages wrap, because it's hard to tell
when one message ends and the next message starts. This just colors the first
line of each stacktrace, based on whether it's a warning or an error. If
messages are being sent to a terminal, it colors them with terminal escape
codes, otherwise it colors them with HTML (ideas for more intelligent behavior
here are welcome).
=head1 BUGS
No known bugs.
Please report any bugs through RT: email
C<bug-carp-always-color at rt.cpan.org>, or browse to
L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Carp-Always-Color>.
=head1 SEE ALSO
L<Carp::Always>
=head1 SUPPORT
You can find this documentation for this module with the perldoc command.
perldoc Carp::Always::Color
You can also look for information at:
=over 4
=item * AnnoCPAN: Annotated CPAN documentation
L<http://annocpan.org/dist/Carp-Always-Color>
=item * CPAN Ratings
L<http://cpanratings.perl.org/d/Carp-Always-Color>
=item * RT: CPAN's request tracker
L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Carp-Always-Color>
=item * Search CPAN
L<http://search.cpan.org/dist/Carp-Always-Color>
=back
=cut
1;
|
