nelson@epiwrl.epi.com (Ken Nelson) (01/15/91)
I am having trouble with the "set filec" option of Sun's csh. It works fine in xterms, but doesn't work when I am using OpenLook's shelltool or cmdtool. Has anybody encountered this? If so is there a way to get the "set filec" option working in a shelltool or cmdtool? Symptoms: The user hits escape, the appropriate filename completions are seen, but appear to have no effect.
rdong@boole.msri.org (Rui-Tao Dong) (01/23/91)
In article Ken Nelson writes: >Symptoms: > >The user hits escape, the appropriate filename completions are seen, but >appear to have no effect. This is a bug for cmdtool under both SunView and OpenWin. A simple trick to get around it is to run "rsh hostname" from that window. You might want to do the following after "rsh" to get suntools working % setenv WINDOW_PARENT '/dev/win0' % setenv WMGR_ENV_PLACEHOLDER '/dev/win1' Rui - Tao Dong | (415) 237 - 7628 (H) 110 Lakeshore Court | (415) 643 - 6048 (O) Richmond, CA 94804 | rdong@borel.msri.org
guy@uunet.uu.net (Guy Harris) (01/27/91)
>This is a bug for cmdtool under both SunView and OpenWin. A simple trick >to get around it is to run "rsh hostname" from that window. Yup, that basically just permanently shoves the "cmdtool" into "uncooked/no echo" mode, so that it merely passes keystrokes through to the tty driver, rather than taking over the canonicalization functions of the tty driver and interpreting keystrokes itself. The problem with C shell filename completion is that, in order to do filename completion in cooked mode, it performs some rather unnatural acts with the tty driver, and 1) the pseudo-tty driver can't notify the "cmdtool" code about "ioctl"s on the slave side in a fashion sufficiently pleasant to make that work ("fixed in S5R4") and 2) even if it could, the "cmdtool" code's ideas of what it should to in order to take over the tty driver's canonicalization functions don't include coping with a program doing Weird Stuff like a bunch of TIOCSTI's in no-echo mode followed by some more TIOCSTI's in echo mode. I've noticed several complaints that this doesn't even work in *shelltool* in Open Windows; I haven't been able to reproduce that myself under OW, and in one case the person later said "it really only happens in cmdtool". Do the "shelltool"s in which this happens have scrollbars? If so, even if they were started by typing "shelltool" and even if they say "shelltool", they're probably really "cmdtool"s.