Message-Id: <9001052321.AA01220@fries.MIT.EDU>
To: irbusch@ATHENA.MIT.EDU
From: Chris VanHaren <vanharen@MIT.EDU>
Subject: Re: mwm 
Date: Fri, 05 Jan 90 18:21:04 EST
Sender: vanharen@ATHENA.MIT.EDU

>> Well, I've gone back to mwm again but I can't wait `til I get some 3100's;
>> its ungodly slow on a VS II.

I know what you mean.  This situation will improve slightly with the
6.4R release (coming end of January).  The mwm in that release has had
some performance enhancements made to it, especially in the area of
focus-switching between windows.  The borders still flicker if you move
around a lot of windows rapidly, but if you type while the borders are
still flashing, the input will go the the correct window most of the
time.  It's still not perfect, but much better than before, and if you
don't aggravate the problem by moving the mouse among lots of windows
very rapidly, you should have better luck -- ie. you *can* make it fail
if you really want to, but shouldn't normally experience it, I hope.

>>  I have a question though.  Is there any way
>> to prevent the console window from jumping into the foreground every time I 
>> create a window out of the WindowOps menu (outside of hiding the window 
>> al-togther)?

Hmm.  This doesn't happen to me.  Perhaps because I am running under 6.4
right now, and you're still on 6.3.  Unfortunately, I have no 6.3
machine to test it on, so I can't say for sure that that is the problem.
If you think of it, ask me again after you get the new release.  I'd
really be interested to know if the problem persists.

>>  And better yet, getting it to not jump out of hiding if I use
>> the mwm menu to kill a window resulting in an xterm: broken pipe error?

That is a little more difficult.  The xterm sends this message to the
console when it dies, and the console dutifully pops up and displays it.
I suppose this is better than the black-bar error messages anyway, but
not much.

There is a program on the "watchmaker" locker that you may be interested
in.  It is called "xconsole", and you can do this:

		xconsole  -u  3  &

This will unmap the console window 3 seconds after it is mapped, every
time it pops up.  You might want to run this at 1 second, even...  You
can run this out of your .startup.X, if you like.  It also takes an
option to map the console:

		xconsole  -m

so that you can pop it up whenever you want to...


>> Thanks much,
>> 
>> 			Ian
>> 			irbusch@athena

					    I hope this helps...
						Chris VanHaren