repeat messages

[bsv00@eng.amdahl.com (Brian Vickery)]

Does anyone know why this message keeps getting sent out?  How do I go about
killing it?  Am I the only one getting it which would lead me to believe it's
somewhere on my system that is screwing up?

~Brian
bsv00@ras.amdahl.com

Newsgroups: fi.clim
From: chyde@labs-n.bbn.com
Subject: (None given)
Apparently-To: <clim@bbn.com>
Original-To: clim@LABS-N
Reply-To: chyde@BBN.COM
Organization: NASA/ARC Information Sciences Division
Date: Mon, 31 Jan 1994 21:19:10 GMT

Sender: news@kronos.arc.nasa.gov
Approved: fi.clim@news.kronos.arc.nasa.gov

Sender: news@kronos.arc.nasa.gov
Approved: fi.clim@news.kronos.arc.nasa.gov

Sender: news@kronos.arc.nasa.gov
Approved: fi.clim@news.kronos.arc.nasa.gov

Sender: news@kronos.arc.nasa.gov
Approved: fi.clim@news.kronos.arc.nasa.gov

Sender: news@kronos.arc.nasa.gov
Approved: fi.clim@news.kronos.arc.nasa.gov

#+Allegro-4.2-final
#+CLIM-2.0-final

is there a way to tell define-command that one command is to be based on
lowercase-a and another is uppercase-A ? 

I have an unpleasantly large need to do this right now, and it appears
that define-command (or something else that uses the results) doesn't
care, and assumes that #\a and #\A are equivalent.

or, perhaps better still, is there a way to define a command so that it
knows what keystroke it was called with?  (not normally important, but
since #\a and #\A both call the same command, it'd be good if the
command received its keystroke somehow...)

 -- clint