erast1@unix.cis.pitt.edu (Evan R Aussenberg) (02/11/91)
In article <1991Feb10.015709.16848@scuzzy.in-berlin.de> src@scuzzy.in-berlin.de (Heiko Blume) writes: >i just found a really nice bug that shows up with tcsh... What about trying "man" with tcsh & isc; I got the man script to run under "sh" but somehow shell variables are not being interpreted correctly and "man" can never find any entries I ask for. "set | more" or "set | less" doesn't seem to pipe correctly. When the display gets to line 24 (or 25) you get the message "suspended (ttyinput)" and tcsh puts the process into the background. Also- would be nice if a patch (probably real small) could be applied to make tcsh vpix aware ($DOSPATH, *.exe, *.bat, *.com). -- Evan Ron Aussenberg erast1@unix.cis.pitt.edu IN%"erast1@pittunix"
aschaffe@polyslo.CalPoly.EDU (JedHead) (02/11/91)
So then erast1@unix.cis.pitt.edu (Evan R Aussenberg) said.. > >What about trying "man" with tcsh & isc; I got the man >script to run under "sh" but somehow shell variables are >not being interpreted correctly and "man" can never find >any entries I ask for. I had the same problem -- it can be fixed by inserting: #!/bin/sh as the first line of all of your shell scripts. (like 'man') [Note: This worked under ISC 2.2 -- I don't know or care about SCO. It also assumes that "sh" is in /bin .. :-) ] Allan -- A top Mideast expert at a major American university pointed out that there is one final chance for a diplomatic solution to the Persian Gulf crisis that hasn't been tried. The United States must send a message to Saddam Hussein saying "SIMON SAYS get out of Kuwait."