Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh-3.0.3: another problem in Src/jobs.c
- X-seq: zsh-workers 3305
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: zsh-3.0.3: another problem in Src/jobs.c
- Date: Tue, 24 Jun 1997 20:10:12 -0700
- In-reply-to: <9706250110.AA01977@xxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <9706250110.AA01977@xxxxxxxxxxxxxxxxxxxxxxxxx>
On Jun 25, 10:10am, SUZUKI Hisao wrote:
} Subject: Re: zsh-3.0.3: another problem in Src/jobs.c
}
} IMHO, the problem is inherent in Un*x.
That's a ridiculous statement. All the necessary tools are available to
get it right; I've written programs that do. It's just that most don't,
because they're not expecting to ever be backgrounded; so they don't do
the necessary checks for process groups and SIGTTIN/TTOU handling. In
vi's case, that's most likely because it was originally written before
job-control shells even existed. (If you really mean elvis or vim or
some such, they have no excuse at all.)
However, you're right that changing zsh is the best idea. Tty management
is complicated, and shells that do their own sophisticated editing and
display management make it more so. There's always going to be somebody
too lazy or inexperienced to make his code clean up after itself properly,
so it behooves zsh to make sure the terminal is functional when it wants
to use it.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
Messages sorted by:
Reverse Date,
Date,
Thread,
Author