Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site imsvax.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!cvl!elsie!imsvax!harris From: harris@imsvax.UUCP Newsgroups: net.unix Subject: grep is not broken Message-ID: <226@imsvax.UUCP> Date: Mon, 20-Aug-84 13:36:27 EDT Article-I.D.: imsvax.226 Posted: Mon Aug 20 13:36:27 1984 Date-Received: Wed, 22-Aug-84 05:25:12 EDT Organization: IMS Inc, Rockville MD Lines: 20 To all those who answered my question is grep broken, thank you but enough is enough. I have been inundated with mail on the subject. I KNOW that grep is not broken. When I posted the article I accidently left out the '^' in the command. I had tried numerous variations including grep '^am.le' /usr/dict/words which yielded among other words 'ampule'. Obviously I thought that was an error. That was what I meant when I wrote that grep had returned a word that was too long. The next day when I logged in again and tried the same grep command. Grep worked correctly and did not return 'ampule'. I do not think this is a figment of my imagination since two witnesses saw the same response. There is of course the possibility of gremlins in the VAX. Although I do not know the exact cause of the problem I believe it is related to other strange results I have seen in 'vi'. The problems are generated when I use 'cu' to connect from our local VAX running 4.2 to a remote VAX running 4.1. The solution I have found is to reset the terminal, a VT100, and to reinitialize the shell. I have not had the time to investigate the exact cause of the problem. -- Harris Reavin UUCP: {umcp-cs!eneevax || seismo!rlgvax!elsie}!imsvax!harris