[1107] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next next in chain last in chain last

Re: [COLD] minimal core

daemon@ATHENA.MIT.EDU (Sat Oct 26 14:05:48 1996 )

To: Brandon Gillespie <brandon@glacier.cold.org>, coldstuff@cold.org
In-reply-to: Your message of "Sat, 26 Oct 1996 11:22:45 MDT."
             <Pine.NEB.3.95.961026111915.18633A-100000@glacier.cold.org> 
Date: Sat, 26 Oct 1996 12:52:49 -0500
From: Zachary DeAquila <zachary@zachs.place.org>

On Saturday, Oct 26, 1996, Brandon Gillespie writes:
>On Sat, 26 Oct 1996, Zachary DeAquila wrote:
>> Well, I decided to mess around a bit with the latest driver, so I
>> compiled it up on my linux box (no problems at all.. very cool) and
>> pulled a brand new Minimalcore out of the box and ran it.
>
>I'm hoping to have another ALPHA4 core available today--with @build and
>company fixed.
>
>> Except:
>> It has one command, QUIT. Said command doesn't seem to work.
>> 
>> Really. I mean it. I type QUITE and it responds with Goodbye.
>> but I stay connected.  Anyone care to explain this?  I read the code
>> and it all seems to look okay.  I don't grok.
>
>Erm, it should have said:
>
>  > QUIT
>  Oops, `QUIT` is not supported here.  Try `@quit`
>  Use `@help commands` for an explanation on the differences in commands.
>
>There is an object in your command cache that knows a few of the
>unsupported commands, and points you in the right direction (I opted to do
>this rather than dirty up the actual command environment with lots of
>different awkward non-standard (by my standards :) aliases)  Use the
>command '@which QUIT' to see all of the places it shows up (@which does
>not check command aliases, as they are from a different parser).

Uh, this is MINIMALCORE-3.2.  You're talking about ColdCore.  

>Typing QUITE does:
>
>  I don't understand QUITE.

erp. that was a typo on my part. I really typed QUIT.

Under MinimalCore-3.2.  Really. Not Coldcore. or CDC or anything like that.
MinimalCore.   Someone else already acknowledged that it was broken in 
private email and said he'd u/l'd a fix to /Incoming  already.

 --Zachary