Path: utzoo!mnetor!uunet!husc6!rutgers!sunybcs!bingvaxu!leah!uwmcsd1!marque!gryphon!richard
From: richard@gryphon.CTS.COM (Richard Sexton)
Newsgroups: comp.sys.amiga
Subject: Re: Shell 2.07m bug (I don't think so)
Message-ID: <2581@gryphon.CTS.COM>
Date: 14 Dec 87 07:03:52 GMT
References: <8712120433.AA24764@decwrl.dec.com>
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 24
Summary: Oh yeah ?

Steve Drew writes:
>
>There is no such bug in 2.07M, I'm sure of it. I have been very careful
>to check the size of the command after finding out from a previous version
>that manx fexec code only allows us 40 chars for a command name. If you
>type a command over about 110 chars without any spaces you will get an error
>message "Error in command name" (same as normal CLI). 
>
>Are you running CONMAN ? (it would have to handle the command line first).
>
>Are you sure you are running an original version of Shell 2.07M ?
>(its possible that a bug like this did exist in older versions of shell)


Bug confirmed in V2.05M...

Funny how I never noticed this after using it for so long, but then
I whenever I rest a book on the keyboard and get three lines of junk,
or the kid braps on the keyboard, I always get a kick out of how fast the
text is erased when I ctrl-X. I hit return this time and....

Holy Bagwan Rajneesh, Batman, it's Mr. Guru.

Guess it's time time to update.