Date: Sun, 7 Sep 1997 02:21:24 -0700 From: Ken McGlothlen <mcglk@yang.cpac.washington.edu> To: freebsd-questions@freebsd.org Subject: tcsh, stty, and other oddities. Message-ID: <199709070921.CAA16958@yang.cpac.washington.edu>
index | next in thread | raw e-mail
Pardon the length of this message, but I'd rather include everything the first
time.
I'm making the switch from a SunOS system to a FreeBSD solution. Frankly, it's
a switch that, theoretically, I'd be wildly happy about except for one thing.
It's my terminal. I think.
The SunOS system I'm currently using it an old reliable SunOS 4.1.1---none of
this Solaris stuff---and it is running tcsh 6.01.00. I access it mostly from a
Macintosh running NCSA Telnet 2.7b4, but also from a FreeBSD 2.2.1 system
running XFree86. Everything works---tcsh supports file completion with the
<TAB> key, ^C works as an interrupt, ^Z suspends, and so on.
Unfortunately, when I use the same software on a FreeBSD 2.1.7.1-RELEASE
system, or a FreeBSD 2.2.1-RELEASE system, I don't get filename completion;
instead, the terminal beeps and nothing happens. Furthermore, on occasion, ^C
doesn't interrupt a process---instead, it suspends it. ^Z does nothing on
those occasions. Emacs completely freaks out---keys quit working unless I hit
a <CR>, which occasionally gets the proper results, but screen updates are
difficult at best, and ^Z doesn't work, and ^X^C only suspends the process, and
so on. Both of the systems are running tcsh 6.06.00, but I don't think there's
anything substantially different in the operations.
Identical setups. Different results.
Now, granted, they both have different versions of stty. The SunOS system is
currently using (with stty -a):
speed 38400 baud, 71 rows, 80 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
erase kill werase rprnt flush lnext susp intr quit stop eof
^? ^U ^W ^R ^O ^V ^Z/^Y ^C ^\ ^S/^Q ^D
The FreeBSD 2.1.7.1-RELEASE system has (with stty -a):
speed 9600 baud; 24 rows; 80 columns;
lflags: icanon isig iexten echo echoe echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
extproc
iflags: -istrip icrnl -inlcr -igncr ixon -ixoff -ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr oxtabs
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow
-dtrflow -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
min = 1; quit = ^\; reprint = ^R; start = ^Q; status = <undef>;
stop = ^S; susp = ^Z; time = 0; werase = ^W;
and the FreeBSD 2.2.1-RELEASE system has exactly the same, except that extproc
has been changed to -extproc. (But then, the 2.1.7 system is at my ISP, and
the 2.2.1 system is at my home.)
The curious thing is that if I set -oxtabs on the FreeBSD systems, file
completion works fine (which doesn't make sense to me, since that's the
*output* of the tabs), but occasionally, ^Z and ^C don't work, and also on
occasion, <TAB> starts echoing as ^I rather than as some number of spaces.
Anyone ever heard of this? Until I get this behavior fixed, I'm reluctant to
make the switch, but I have a limited time before I have no choice but to make
the switch.
I'm not on the freebsd-questions list, so please E-mail me directly at one of
the addresses below:
---Ken McGlothlen
mcglk@serv.net
mcglk@cpac.washington.edu
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709070921.CAA16958>