view release on metacpan or  search on metacpan

README  view on Meta::CPAN

      2. The older versions of Term::ANSIColor dependency do not recognize
      bright/RGB settings, falling back to the default behavior (plain 16
      colors). However, the whole Term::ANSIColor is optional, it is only
      required to preview the effects of the "OPTIONS" via command line
      before actually editing the ~/.tmux.conf. That is, rainbarf --bright
      --tmux is guaranteed to work despite the outdated Term::ANSIColor!

    Another option is skipping the system colors altogether and use the RGB
    palette (rainbarf --rgb). This fixes the issue 1, but doesn't affect
    the issue 2. It still looks better, though.

 Persistent storage

    CPU utilization stats are persistently stored in the ~/.rainbarf.dat
    file. Every rainbarf execution will update and rotate that file. Since
    tmux calls rainbarf periodically (every 15 seconds, by default), the
    chart will display CPU utilization for the last ~9.5 minutes (15 * 38).
    Thus, several tmux instances running simultaneously for the same user
    will result in a faster chart scrolling.

rainbarf  view on Meta::CPAN

=item 2.

The older versions of L<Term::ANSIColor> dependency do not recognize bright/RGB settings, falling back to the default behavior (plain 16 colors).
However, the whole L<Term::ANSIColor> is optional, it is only required to preview the effects of the L</OPTIONS> via command line before actually editing the F<~/.tmux.conf>.
That is, C<rainbarf --bright --tmux> B<is guaranteed to work> despite the outdated L<Term::ANSIColor>!

=back

Another option is skipping the system colors altogether and use the B<RGB> palette (C<rainbarf --rgb>).
This fixes the I<issue 1>, but doesn't affect the I<issue 2>.
It still looks better, though.

=head2 Persistent storage

CPU utilization stats are persistently stored in the F<~/.rainbarf.dat> file.
Every L<rainbarf> execution will update and rotate that file.
Since C<tmux> calls L<rainbarf> periodically (every 15 seconds, by default), the chart will display CPU utilization for the last ~9.5 minutes (15 * 38).
Thus, several C<tmux> instances running simultaneously for the same user will result in a faster chart scrolling.

=head2 screen