Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: coloring STDERR to terminal

X-seq: zsh-users 7616
From: Vincent Lefevre <vincent@xxxxxxxxxx>
To: zsh-users@xxxxxxxxxx
Subject: Re: coloring STDERR to terminal
Date: Tue, 29 Jun 2004 18:08:26 +0200
In-reply-to: <Pine.LNX.4.60.0406280815130.19831@xxxxxxxxxxxxxxxxxx>
Mail-followup-to: zsh-users@xxxxxxxxxx
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <20040627190433.Q27888@willy_wonka> <Pine.LNX.4.60.0406280815130.19831@xxxxxxxxxxxxxxxxxx>
Sender: Vincent Lefevre <vincent@xxxxxxxxxx>

On 2004-06-29 08:43:50 -0700, Bart Schaefer wrote:
> This sort of thing is the reason that zsh's coprocess hangs around after 
> its input and output are closed, rather than exiting the way ksh coprocs
> do.  Assuming you're not using the coprocess for anything else (hardly
> anyone does) you can do this:
> 
>  coproc while read line; print '\e[91m'${(q)line}'\e[0m' > /dev/tty
>  exec 2>&p

It doesn't work very well. Normally, if I do a Ctrl-d when there are
running jobs, I get:

greux:~>
zsh: you have running jobs.
greux:~>

With the coprocess, I get:

greux:~>
greux:~> zsh: you have running jobs.

-- 
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/>
100% validated (X)HTML - Acorn / RISC OS / ARM, free software, YP17,
Championnat International des Jeux Mathématiques et Logiques, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Follow-Ups:
- Re: coloring STDERR to terminal
  - From: Bart Schaefer

References:
- coloring STDERR to terminal
  - From: Atom 'Smasher'
- Re: coloring STDERR to terminal
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author