From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from drizzle.Stanford.EDU ([36.59.0.16]) by hawkwind.utcs.toronto.edu with SMTP id <24108>; Wed, 26 Jan 1994 11:05:56 -0500
Received: from localhost (castor@localhost) by drizzle.Stanford.EDU (8.6.4/8.6.4) id IAA20920; Wed, 26 Jan 1994 08:05:43 -0800
From:	Castor Fu <castor@drizzle.Stanford.EDU>
Message-Id: <199401261605.IAA20920@drizzle.Stanford.EDU>
Subject: Re: yet another creeping feature suggestion
To:	arnold@cc.gatech.edu (Arnold Robbins)
Date:	Wed, 26 Jan 1994 11:05:42 -0500
Cc:	sam-fans@hawkwind.utcs.toronto.edu
In-Reply-To: <199401261533.KAA05176@penfold.cc.gatech.edu> from "Arnold Robbins" at Jan 26, 94 10:33:03 am
X-Mailer: ELM [version 2.4 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII

Arnold Robbins (sp?) says
> 
> The discussion about sam features and alternate samterms brings to mind
> the "feature" I'd really like to see in samterm, which is some way to
> add things to the button 3 menu.  In particular, I'd like to be able to
> add some way to send my own strings at the sam command window.  This comes
> up most often when I'm hacking text, and I'd love to be able to use a
> menu item to send ``|fmt'' at the command window.
> 
> P.S. And no, it should not be done as X resources! Gack. A .samtermrc
> suits me fine.
> 

Great. . . Seriously, while X-windows resource formats can be ugly, I
am not convinced that they have to be worse than learning yet another
startup file format.

Perhaps the correct solution for those wanting more "customization"
would be to build a samterm interface to tcl/Tk.  Then the interface
code  would be in a format that at least some people could easily
modify.

	-castor