zsh-workers
 help / color / mirror / code / Atom feed
From: "stringfellow.n.d" <stringfe@rmcs.cran.ac.uk>
To: zsh-workers@math.gatech.edu
Subject: Re: terminal parameter changed problem
Date: Mon, 02 Feb 1998 16:16:02 +0000	[thread overview]
Message-ID: <34D5F142.6487@rmcs.cran.ac.uk> (raw)
In-Reply-To: <9802020353.AA22474@ezdzit.zko.dec.com>

Paul Lew wrote:
> 
> Is there a fix for the terminal parameter changed problem?  Some of the
> terminal parameters got turned off after executing some commands, in
> particular, susp, dsusp, discard, quit, and lnext all got
> reset to <undef>.  This virtually shut down the job control ability.
> 
> This has been reported before but I did not see a fix for it.
> Contraray to what has been reported before, these commands do not have
> to be backgrounded.
> 

The previous advice given was to use 

ttyctl -f

to freeze the terminal.
However, as useful as this work-around is, it would be nicer to have a
patch,
so ...

http://mason.primenet.com.au/zsh/workers-1997-hyper/0567.html

provides the answer (included below).
This patch was for zsh 3.0.3 but I think that it should work for later
versions - although it's small enough to edit the file Src/jobs.c by
hand. 

This patch doesn't appear to have made it into later versions of zsh,
i.e.
it was only ever reported as a patch and slipped through the net when
later
versions were produced.

Patch for tty problem:-

Here is Peter's patch:

*** ./Src/jobs.c.old Wed Jun 4 17:51:43 1997
--- ./Src/jobs.c Wed Jun 4 17:53:39 1997
***************
*** 155,161 ****
}
}

! if (shout && !ttyfrozen && !jn->stty_in_env)
gettyinfo(&shttyinfo);

if (isset(MONITOR)) {
--- 155,161 ----
}
}

! if (shout && !ttyfrozen && !jn->stty_in_env && inforeground)
gettyinfo(&shttyinfo);

if (isset(MONITOR)) {


  reply	other threads:[~1998-02-02 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-02  3:53 Paul Lew
1998-02-02 16:16 ` stringfellow.n.d [this message]
1998-02-02 16:55   ` Paul Lew
1998-02-02 17:56     ` stringfellow.n.d

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=34D5F142.6487@rmcs.cran.ac.uk \
    --to=stringfe@rmcs.cran.ac.uk \
    --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).