From: Andy Spiegl <zsh.Andy@spiegl.de>
To: zsh-users@sunsite.dk
Subject: Re: coloring STDERR to terminal
Date: Fri, 30 Jul 2004 13:50:24 +0200 [thread overview]
Message-ID: <20040730115024.GA25889@spiegl.de> (raw)
In-Reply-To: <20040702124259.GS2033@ay.vinc17.org>
Hi everyone,
I'd followed the discussion closely because I also thought coloring of
stderr to be a great thing to have. I ended up using Vincents way:
> exec 2>>(while read line; do
> print '\e[91m'${(q)line}'\e[0m' > /dev/tty; done &)
Which seems to work nicely, well except for the reordering of lines
sometimes, but I could live with that.
However there is one situation where output not only is out of order but
doesn't appear at all:
condor% echo $ZSH_VERSION
4.2.0
condor% touch foo bar
condor% cp -i foo bar
cp: overwrite `bar'? y
condor% exec 2>>(while read line; do print '\e[91m'${(q)line}'\e[0m' > /dev/tty; done &)
condor% cp -i foo bar
y
As you can see the question doesn't appear at all!
But when I then do this, it suddenly appears:
condor% echo test >&2
condor% cp: overwrite `bar'? test
So it seems that zsh doesn't flush some buffer?
Is that a zsh-bug or a problem with this exec-trick?
Chau,
Andy.
--
o _ _ _
------- __o __o /\_ _ \\o (_)\__/o (_) -o)
----- _`\<,_ _`\<,_ _>(_) (_)/<_ \_| \ _|/' \/ /\\
---- (_)/ (_) (_)/ (_) (_) (_) (_) (_)' _\o_ _\_v
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The brain is a wonderful organ; it starts working the moment you get up
in the morning, and does not stop until you get to work.
next prev parent reply other threads:[~2004-07-30 11:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 23:22 Atom 'Smasher'
2004-06-28 0:06 ` ari
2004-06-28 0:36 ` Atom 'Smasher'
2004-06-29 15:43 ` Bart Schaefer
2004-06-29 16:08 ` Vincent Lefevre
2004-06-29 17:14 ` Bart Schaefer
2004-06-30 7:09 ` Vincent Lefevre
2004-06-30 10:52 ` Bart Schaefer
2004-06-30 11:43 ` Vincent Lefevre
2004-06-30 12:01 ` Vincent Lefevre
2004-06-30 16:56 ` Bart Schaefer
2004-07-01 18:14 ` Vincent Lefevre
2004-07-02 0:11 ` Bart Schaefer
2004-07-02 12:42 ` Vincent Lefevre
2004-07-02 21:32 ` Bart Schaefer
2004-07-20 9:10 ` Atom 'Smasher'
2004-07-20 16:10 ` Bart Schaefer
2004-07-20 19:27 ` Atom 'Smasher'
2004-07-20 21:15 ` Bart Schaefer
2004-07-20 23:30 ` Wayne Davison
2004-07-21 3:15 ` Bart Schaefer
2004-07-21 6:23 ` Wayne Davison
2004-07-21 7:30 ` Bart Schaefer
2004-07-21 13:19 ` Vincent Lefevre
2004-07-30 11:50 ` Andy Spiegl [this message]
2004-07-30 23:44 ` Vincent Lefevre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040730115024.GA25889@spiegl.de \
--to=zsh.andy@spiegl.de \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).