On Wed, Jan 28, 2009 at 09:33:25PM EST, Joe Zbiciak wrote:
> Chris Jones wrote:
>
>
> > I need to conform to screen's "STRING ESCAPES" syntax for coloring and
> > therefore I can't just use the underlying xterm's ctlseq's as I was
> > naively trying to do. :-(
> >
> > Or to put it another way,
Chris Jones wrote:
> I need to conform to screen's "STRING ESCAPES" syntax for coloring and
> therefore I can't just use the underlying xterm's ctlseq's as I was
> naively trying to do. :-(
>
> Or to put it another way, since screen's syntax only supports 8+8 colors
> via the "color" letters [k
On Wed, Jan 28, 2009 at 01:50:44PM EST, Adrian Rollett wrote:
> I've found that the only way to implement something like this is to
> have your backtick script vary the output according to the
> temperature. For instance, here's a fragment from a script I use to
> output the current disk use, col
I've found that the only way to implement something like this is to
have your backtick script vary the output according to the temperature.
For instance, here's a fragment from a script I use to output the
current disk use, colored according to percentage used:
if [[ "${PERCENTAGE}" -lt 85
My hardstatus line invokes fairly elaborate backticks that tell me all I
need to know about the current state of my system.
I was thinking of making it more readable by enhancing it with a bit of
color.
One backtick for instance tells me how hot my system is running and
since /proc/acpi/thermal_z