You didn't say you wanted a GUI program.

No, I didn't. My point was an ease-of-use thing.  I have no idea what
the (negative half moon) key is _called_, but if I could point to its
picture, maybe I could find out, or maybe just use it anyway.

	Use xkeycaps (a frontend to xmodmap) if you want.
	I think it is installed on Suns by default,

Not in this straight-out-of-the-box Solaris 2.8 it's not.

(Don't you just love the way I keep being pointed to X utilities that
are either not in the standard $PATH or not there at all?  Welcome to
the wonderful world of X.  I just hope MacOS X doesn't imitate _that_
part of UNIX.)

	if not, you can get it at http://www.jwz.org/xkeycaps.

Thank you very much.  I am greatly indebted to you for telling me about
this fine program.  60 students would have been thrilled to the very socks
to have it last week, so I shall ask our sysadmin to install it.

	Still, you probably do not want to use xkeycaps in every
	session, but write the changed settings into your .xmodmap (or
	whatever) file.
	
I really must have been unclear.  I'm not talking about *my* setup,
which actually works fairly well.  I'm talking about *temporarily*
changing setup so that I can demonstrate something on *someone else's*
machine.  For that, permanent changes to .xmodmap would be quite
inappropriate.

	> What do you mean "misconfigured"?  I never said that my X system or anyone
	> else's X system was misconfigured, only that they *differ*.
	
	I call a different keymapping between X and the console a
	"misconfiguration".

You aren't quite reading what I wrote.
Here it is again:
	I never said that [my X system] or [anyone else's X system]
	was misconfigured, only that [they] differ.
That is, person A has a consistent configuration, person B has a
consistent configuration, and person A has to help person B, so needs
to change *one* thing and have the entire environment adjust, then
change *one* thing back to what it was.  If you just use stty, or you
just use xmodmap, *then* things become inconsistent.

	Also, if you want X to send BackSpace and it is configured to
	not do so, it's not configured correctly for your needs.
	
Remember, person A and person B are *different people*, as well as using
different machines.

	> and that it would be well if Squeak adapted automatically.
	
	Nope. Squeak as an X application should use the X keymappings and nothing
	else.
	 
In a recent thread about GUIs, I thought there was agreement that Squeak
should be *better* than X.

	X does its job. There is room for improvement, of course.

Yeah, like performance, consistency, documentation, you name it.
I look back on the days when I used a Xerox Dandelion with regret;
a simple snappy window system on what was basically a 16-bit machine
that could run rings around this 64-bitter, with documentation you
could actually read in one human lifetime.  (*AND* it handled a 16-bit
character set with dynamically selectable virtual keyboards.  On a
machine with 4MB of physical memory and a hard limit of 32MB virtual.)
I have two dtterms, netscape, and a clock.  For this I need 212 MB of
virtual memory?

Big as it is, Squeak is DWARFED by the X monster.