Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: coloring stderr - was Re: piping stderr
- X-seq: zsh-users 14131
- From: Atom Smasher <atom@xxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: coloring stderr - was Re: piping stderr
- Date: Mon, 18 May 2009 18:09:27 +1200 (NZST)
- In-reply-to: <20090518004044.GI27141@xxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- Openpgp: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt
- References: <20090514104908.98556.qmail@xxxxxxxxxxx> <691a5d910905140904p538d5343md0712590db983853@xxxxxxxxxxxxxx> <20090515114736.33891.qmail@xxxxxxxxxxx> <4A0DD7D7.40500@xxxxxxxxxxxxx> <20090516002553.91142.qmail@xxxxxxxxxxx> <20090518004044.GI27141@xxxxxxxxxxxxxxxxxxx>
On Mon, 18 May 2009, Vincent Lefevre wrote:
but it's still got some unintended consequences... the problem i'm
having now with it is that if i start bash as a child of zsh, bash is a
bit messed up.
I can notice that the bash prompt doesn't appear, because bash has not
been started in interactive mode ('i' is not in "$-"). If I force
interactive mode, I get:
prunille:~> bash -i
zsh: suspended (tty input) bash -i
=================
yeah, that counts as messed up ;)
http://smasher.org/tmp/snapshot153.png
it's not every day that something on the command line dies from SIGTTIN.
back to the drawing board....
--
...atom
________________________
http://atom.smasher.org/
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
"That's hard to tell. I think that, you know, I would hope
to be able to convince people I could handle the Iraqi
situation better."
-- George "dubya" Bush
Bush-Gore debate, 11 Oct 2000
Messages sorted by:
Reverse Date,
Date,
Thread,
Author