[1106] 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 13:28:46 1996 )

Date: Sat, 26 Oct 1996 11:22:45 -0600 (MDT)
From: Brandon Gillespie <brandon@glacier.cold.org>
To: Zachary DeAquila <zachary@zachs.place.org>
cc: coldstuff@cold.org
In-Reply-To: <m0vH4iM-00014qC@zachs.place.org>

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).

Typing QUITE does:

  I don't understand QUITE.

Do you have any command aliases?  One of those could be conflicting, try:

  @command-aliases|@ca

See what you have defined..

-Brandon