RE: [cobalt-developers] Control + S lockup.

["Matthew Nuzum" <cobalt@xxxxxxxxxxxxx>]

> This is something a UNIX old-timer like myself can help out with.
> 
> Control-S is part of an old line discipline, which specifies that ^S
is
> the XOFF code, and ^Q is XON.  (This is actually the definition of
these
> codes in the ASCII standard.)  Many TTY line drivers interpret ^S as
> a request to suspend output, while ^Q will resume.
> 
> This behaviour is of course configurable.  Try this command:
>
...
> 
> stty stop ''
> 
> This will unbind the ^S from the stop function.  You can set it back
> with:
> 
> stty stop '^S'   (to enter control S, use control V then control S)
> 
> Normally, a program like EMACS will change the tty settings itself, so
> that ^S
> and ^Q aren't intercepted by the line driver.  Use man stty for more
info.
> 
> 
> cheers
> Paul Gillingwater

Thanks Paul and others who responded.

This works perfectly.  The ^q command does resume everything just fine,
and knowing that is a huge help.  I did set the sty stop '' in my
.profile and I don't have to worry about the problem  anymore.

I should have asked this question a long time ago.  I'm scared to think
of the many times I waited just a little too long to save my changes and
then locked the terminal.

You live and you learn I guess.

Thanks again,

Matthew Nuzum
followers.net