From: suzuki@otsl.oki.co.jp (SUZUKI Hisao)
To: hzoli@ny.frontiercomm.net
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.0.3: another problem in Src/jobs.c
Date: Tue, 24 Jun 97 11:05:37 JST [thread overview]
Message-ID: <9706240205.AA02610@oz.fantasy.otsl.oki.co.jp> (raw)
In-Reply-To: <199706231522.LAA00907@hzoli.home> (message from Zoltan Hidvegi on Mon, 23 Jun 1997 11:22:47 -0400 (EDT))
>> % emacs -nw &
>> % fg
>> [type ^X^C to terminate the emacs]
>> % stty
>>
>> [Note: this is not artificial. When you forget to set
>> DISPLAY, you will be put in the same situation.]
[snip]
>> If solely my patch of June 20 had applied, then this is not
>> happend when you _once_ suspend the "fg"ed emacs job before
>> terminate it. Now that you also changed Src/jobs.c from
>
>But it did happed when you did not suspend the fg'ed job, even with your
>patch, right?
Yes, precisely. However, suspending the fg'ed job was an _easy_
work around to do when you got into the situation. In fact, I
and my colleagues had never noticed that problem before; we
usually suspend emacs of non x-window to switch the jobs.
>Still I think zsh is right here, and it is an emacs bug. The problem is
>emacs leaves the tty setting in a wrong state when it exits. I do not
>know how zsh can help here. Note that ksh does the same, even worse,
>since after this the ksh line editor becomes unusable, and I had to kill
>ksh from an other terminal.
Well, try bash-1.14.7 or tcsh-6.06, please. They get on well
with emacs. It is regrettable that zsh does not. In spite of
its _excellent_ line-editing facility and other useful features,
this particular problem may make zsh _notorious_ as a shell that
is free and powerful but cannot work well even with emacs...
Perhaps, IMHO, the better way to do is:
(1) For zsh-3.0.X, to take a conservative patch as mine for the
time being, and note the problem and works around (ttyctl,
STTY, or job suspending) in Etc/BUGS. Please do not forget
that zsh-3.0.X is being used for _daily_ use by many users
all over the world.
(2) For zsh-3.1.X, to devise an innovation. I think it is best
to make a third option for ttyctl which let the shell
ignore stty changes under some unusual situations (as bash
does). And it will be nice if the new option is default.
--
Hisao Suzuki <suzuki@otsl.oki.co.jp>
next prev parent reply other threads:[~1997-06-24 2:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-23 10:51 SUZUKI Hisao
1997-06-23 15:22 ` Zoltan Hidvegi
1997-06-24 2:05 ` SUZUKI Hisao [this message]
1997-06-24 2:52 ` Zoltan Hidvegi
1997-06-24 11:56 ` SUZUKI Hisao
[not found] <3.0.1.32.19970624091754.01331150@home.incontext.com>
1997-06-25 1:10 ` SUZUKI Hisao
1997-06-25 3:10 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1997-06-19 6:24 SUZUKI Hisao
1997-06-19 7:04 ` Zoltan Hidvegi
1997-06-19 7:26 ` Andrei Tcherepanov
1997-06-19 23:32 ` SUZUKI Hisao
1997-06-20 3:45 ` Zoltan Hidvegi
1997-06-20 8:20 ` SUZUKI Hisao
1997-06-19 8:58 ` Peter Stephenson
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=9706240205.AA02610@oz.fantasy.otsl.oki.co.jp \
--to=suzuki@otsl.oki.co.jp \
--cc=hzoli@ny.frontiercomm.net \
--cc=zsh-workers@math.gatech.edu \
/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).