CLIM mail archive
[Prev][Next][Index][Thread]

Mailer bounces on the CLIM mailing list.

Dear Postmeister,

I've temporarily removed all of the arc.nasa.gov entries from the CLIM
mailing list.   Please correct whatever mailer loop problem that was
causing messages to be resent multiple times.

For those on the CLIM list, this is also a test of non-bouncing.  Please
ignore.  

Thanks,
Dan

----------

   Return-Path: <@bbn.com:news@ptolemy-ethernet.arc.nasa.gov>
   Received: from KARIBA.BBN.COM by life.ai.mit.edu (4.1/AI-4.10) for /com/archive/clim id AA02832; Mon, 31 Jan 94 15:57:21 EST
   Received: from BBN.COM by KARIBA.BBN.COM id aa27032; 31 Jan 94 15:55 EST
   Received: from ptolemy-ethernet.arc.nasa.gov by BBN.COM id aa22121;
             31 Jan 94 15:54 EST
   Received: from kronos-ethernet.arc.nasa.gov by ptolemy.arc.nasa.gov (4.1/) id <AA15844>; Mon, 31 Jan 94 12:54:06 PST
   Newsgroups: fi.clim
   Path: kronos.arc.nasa.gov!@labs-n.bbn.com,@exploder.bbn.com:HYDE@Exploder
   From: chyde@labs-n.bbn.com
   Subject: (None given)
   Message-Id: <2969030058-797825@Exploder>
   Apparently-To: <clim@bbn.com>
   Originator: daemon@ptolemy-ethernet.arc.nasa.gov
   Sender: HYDE@exploder.ai.mit.edu
   Nntp-Posting-Host: ptolemy-ethernet.arc.nasa.gov
   Original-To: clim@LABS-N
   Reply-To: chyde@bbn.com
   Organization: NASA/ARC Information Sciences Division
   Distribution: fi
   Date: Mon, 31 Jan 1994 20:53:07 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
   
   #+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
Main Index | Thread Index