ch42_04.htm

the unix power tools

></BLOCKQUOTE
></P
><P
CLASS="para"
>Call it something like <EM
CLASS="emphasis"
>sane</EM
>.
You may need to execute it by typing
LINEFEED
or
CTRL-j
before and
after.</P
><P
CLASS="para"
>If that doesn't work perfectly, here's what to do.
The next time you log in and your screen works just right,
typing <EM
CLASS="emphasis"
>stty&nbsp;everything</EM
> or <EM
CLASS="emphasis"
>stty -g</EM
> (see below) should
help you decide exactly what parameters to use in your <EM
CLASS="emphasis"
>sane</EM
>
command.</P
></LI
><LI
CLASS="listitem"
><P
CLASS="para"
>If the system seems to treat every character you
type as a separate command (and you may not be able to see the
characters you type):</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>reset</B
></CODE
>
r: Command not found.
: No previous regular expression
: No current filename
: No lines in the buffer<CODE
CLASS="userinput"
><B
>q</B
></CODE
>
%</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-46882"
></A
>
(It actually doesn't look quite like that, but the first <CODE
CLASS="userinput"
><B
>e</B
></CODE
> started
the editor named <EM
CLASS="emphasis"
>e</EM
>.
The <CODE
CLASS="userinput"
><B
>s</B
></CODE
>, <CODE
CLASS="userinput"
><B
>e</B
></CODE
>, and <CODE
CLASS="userinput"
><B
>t</B
></CODE
> are all read as commands by
<EM
CLASS="emphasis"
>e</EM
>.
You have to quit <EM
CLASS="emphasis"
>e</EM
> by typing its <CODE
CLASS="literal"
>q</CODE
> command.
Sheesh!)</P
><P
CLASS="para"
>You should make a shell function or alias&nbsp;- or, put a
<SPAN
CLASS="link"
>symbolic link (<A
CLASS="linkend"
HREF="ch18_04.htm"
TITLE="More About Links "
>18.4</A
>)</SPAN
>
or
shell script in your
<SPAN
CLASS="link"
><EM
CLASS="emphasis"
>bin</EM
> directory (<A
CLASS="linkend"
HREF="ch04_02.htm"
TITLE="A bin Directory for Your Programs and Scripts "
>4.2</A
>)</SPAN
>-
that
lets you run the command from
the previous step (<EM
CLASS="emphasis"
>reset</EM
>, <EM
CLASS="emphasis"
>stty&nbsp;sane</EM
>, etc.) by typing a single
character.
I picked <CODE
CLASS="literal"
>]</CODE
> (right square bracket) as the name of mine.
To make mine, I made a symlink in my <EM
CLASS="emphasis"
>bin</EM
>:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>ln -s /usr/ucb/reset ]</B
></CODE
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>(Your system's <EM
CLASS="emphasis"
>reset</EM
> command may have a different pathname.)
Now, to fix a goofed-up terminal, I just type a <CODE
CLASS="literal"
>]</CODE
> at a shell prompt
(it may need a
LINEFEED
or
CTRL-j
before and after).</P
></LI
><LI
CLASS="listitem"
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-46909"
></A
><A
CLASS="indexterm"
NAME="AUTOID-46912"
></A
>Best of all, if your system has the command <EM
CLASS="emphasis"
>stty -g</EM
>, you can use it to
save your favorite terminal settings in a file.
Then, when your terminal is goofed up, read those settings in again from
the file.
Here's how.
First, when your terminal is working just the way you want it, type:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>stty -g &gt;$HOME/.stty</B
></CODE
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>Then make your alias, shell script, or shell function named <EM
CLASS="emphasis"
>sane</EM
>,
<CODE
CLASS="replaceable"
><I
>]</I
></CODE
>, etc. (previously explained) that runs the command:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>stty `cat $HOME/.stty`</B
></CODE
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>This should restore your terminal the way it was when you first
ran the <EM
CLASS="emphasis"
>stty -g</EM
> command.</P
><P
CLASS="para"
>If your system doesn't have <EM
CLASS="emphasis"
>stty -g</EM
>, you can fake it.
Run the command <EM
CLASS="emphasis"
>stty&nbsp;everything</EM
>
or <EM
CLASS="emphasis"
>stty -a</EM
> and look at the settings:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>stty everything</B
></CODE
>
speed 38400 baud, 0 rows, 0 columns
parenb -parodd cs7 -cstopb -hupcl cread -clocal -crtscts
-ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr icrnl -iuclc
ixon -ixany -ixoff imaxbel
isig iexten icanon -xcase echo echoe echok -echonl -noflsh -tostop
echoctl -echoprt echoke
opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel -tabs
erase  kill  werase rprnt  flush  lnext   susp   intr   quit  stop   eof
^?     ^U     ^W     ^R     ^O     ^V     ^Z/^Y  ^C     ^\   ^S/^Q  ^D</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>Then check your <EM
CLASS="emphasis"
>stty</EM
> manual page and read about those settings
(some of them, like the parity settings, might not be appropriate for all
your login sessions).
Put the settings in your <EM
CLASS="emphasis"
>sane</EM
> or <CODE
CLASS="replaceable"
><I
>]</I
></CODE
> command:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>stty icanon echo erase '^?' kill '^u' ...</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>Note that if you use several different terminals, each may have different
settings.
Make yourself several <EM
CLASS="emphasis"
>sane</EM
> commands; you might
<SPAN
CLASS="link"
>select one automatically as you log in (<A
CLASS="linkend"
HREF="ch02_12.htm"
TITLE="Automatic Setups for Different Terminals "
>2.12</A
>)</SPAN
>.</P
></LI
></UL
><P
CLASS="para"
>If worse comes to worst, try the steps from article
<A
CLASS="xref"
HREF="ch42_02.htm"
TITLE="Fixing a Hung Terminal or Job "
>42.2</A
>.
Find another place to log in to your account.
Run <EM
CLASS="emphasis"
>ps</EM
> to find your processes on the hung-up terminal or window
and kill them.
Then turn off the terminal or close the window and log in again.
(If you didn't have a way to kill the processes before you logged in
again, be sure to kill your old processes right away after you log in.)</P
><DIV
CLASS="sect1info"
><P
CLASS="SECT1INFO"
>- <SPAN
CLASS="authorinitials"
>JP</SPAN
></P
></DIV
></DIV
><DIV
CLASS="htmlnav"
><P
></P
><HR
ALIGN="LEFT"
WIDTH="515"
TITLE="footer"><TABLE
WIDTH="515"
BORDER="0"
CELLSPACING="0"
CELLPADDING="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="172"
><A
CLASS="SECT1"
HREF="ch42_03.htm"
TITLE="42.3 Why Changing TERM Sometimes Doesn't Work "
><IMG
SRC="gifs/txtpreva.gif"
SRC="gifs/txtpreva.gif"
ALT="Previous: 42.3 Why Changing TERM Sometimes Doesn't Work "
BORDER="0"></A
></TD
><TD
ALIGN="CENTER"
VALIGN="TOP"
WIDTH="171"
><A
CLASS="book"
HREF="index.htm"
TITLE="UNIX Power Tools"
><IMG
SRC="gifs/txthome.gif"
SRC="gifs/txthome.gif"
ALT="UNIX Power Tools"
BORDER="0"></A
></TD
><TD
ALIGN="RIGHT"
VALIGN="TOP"
WIDTH="172"
><A
CLASS="SECT1"
HREF="ch42_05.htm"
TITLE="42.5 Checklist: Screen Size Messed Up? "
><IMG
SRC="gifs/txtnexta.gif"
SRC="gifs/txtnexta.gif"
ALT="Next: 42.5 Checklist: Screen Size Messed Up? "
BORDER="0"></A
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="172"
>42.3 Why Changing TERM Sometimes Doesn't Work </TD
><TD
ALIGN="CENTER"
VALIGN="TOP"
WIDTH="171"
><A
CLASS="index"
HREF="index/idx_0.htm"
TITLE="Book Index"
><IMG
SRC="gifs/index.gif"
SRC="gifs/index.gif"
ALT="Book Index"
BORDER="0"></A
></TD
><TD
ALIGN="RIGHT"
VALIGN="TOP"
WIDTH="172"
>42.5 Checklist: Screen Size Messed Up? </TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="515"
TITLE="footer"><IMG
SRC="gifs/smnavbar.gif"
SRC="gifs/smnavbar.gif"
USEMAP="#map"
BORDER="0"
ALT="The UNIX CD Bookshelf Navigation"><MAP
NAME="map"
><AREA
SHAPE="RECT"
COORDS="0,0,73,21"
HREF="../index.htm"
ALT="The UNIX CD Bookshelf"><AREA
SHAPE="RECT"
COORDS="74,0,163,21"
HREF="index.htm"
ALT="UNIX Power Tools"><AREA
SHAPE="RECT"
COORDS="164,0,257,21"
HREF="../unixnut/index.htm"
ALT="UNIX in a Nutshell"><AREA
SHAPE="RECT"
COORDS="258,0,321,21"
HREF="../vi/index.htm"
ALT="Learning the vi Editor"><AREA
SHAPE="RECT"
COORDS="322,0,378,21"
HREF="../sedawk/index.htm"
ALT="sed &amp; awk"><AREA
SHAPE="RECT"
COORDS="379,0,438,21"
HREF="../ksh/index.htm"
ALT="Learning the Korn Shell"><AREA
SHAPE="RECT"
COORDS="439,0,514,21"
HREF="../lrnunix/index.htm"
ALT="Learning the UNIX Operating System"></MAP
></DIV
></BODY
></HTML
>