Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU (Jim Fulton)
Newsgroups: comp.windows.x
Subject: Re: R3, or Where have all the flamers gone?
Message-ID: <8811080021.AA13611@EXPO.LCS.MIT.EDU>
Date: 8 Nov 88 00:21:50 GMT
References: <8811072211.AA11021@M9-514-1.MIT.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 60


> 1)	[how to distinguish xdm logins]

Here is what I do with the default setup.  I have my ~/.xsession

	#!/bin/csh -f
	
	source $HOME/.env.csh

	xrdb -load $HOME/.Xres
	xmodmap $HOME/.xmodmaprc
	xsetroot -solid '#888'
	xset b 100 400 c 50 s 1800 r on
	uwm &
	xclock -geometry 48x48-1+1 &
	exec /usr/bin/X11/xterm -geometry 80x66-0-0 -name hpx $*

If you want to do anything special when you start up an xterm, you could 
set a magic environment variable and to an xterm -ls (so that your .login
could look for your variable).  Or any number of things.  It depends on what
you want to do.  One of the goals for xdm was that it would be flexible enough
to allow you to tailor quickly and easily without writing C code.  The next
step is to write a real session manager.


> 2)	XPutImage though greatly fixed seems to leave holes on expose events
> but only when refreshing XYBitmaps on the QDSS display.

XYBitmaps are still broken on some displays.  As always, send small test
programs to xbugs.


> 3)	Xterm and 'vi' STILL don't get along on long lines that wrap around!?

Nobody contributed fixes for this and we didn't have time to look into it
ourselves (nobody here uses vi).  Attention vi-hackers: you will make new
friends if you fix this and then give it back to us! 


> 4)	My uwm widow manager is quite a bit slower, and doesn't seem to read
> mouse motion very well.

Definitely send a note to xbugs with your .uwmrc, any resources, and explicit
instructions for how to demonstrate the situation.  Uwm does have to do a lot
more work these days, so expect it to be a little slower (window manager
writers, time to start thinking about tracking color map changes among 
other things).  We hadn't noticed, but then that's not very surprising.


> 5)	In this age of toolkits, it would be nice if "uwm" could selectively
> dump subwindows. (Not really an R3 gripe.)  A '-subwindow' option, for
> example, would be nice.

I don't understand what you mean by "dump subwindows".  Do you mean xlswins?
Or xpr?  Or xmag?  In any case, uwm is rapidly reaching the point of needing
a major overhauling.  Once the ICCCM is adopted, we plan to attack it with
very sharp knives....


					Thanks for the feedback,
					Jim