Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!bloom-beacon!ATHENA.MIT.EDU!phils
From: phils@ATHENA.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: R3, or Where have all the flamers gone?
Message-ID: <8811072211.AA11021@M9-514-1.MIT.EDU>
Date: 7 Nov 88 22:11:14 GMT
References: <8811072007.AA10984@EXPO.LCS.MIT.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 28


	Okay, here are a few problems with R3 and things on my wish list for
next (just in time for Christmas) release.

1)	When logging into the console, it was previously possible to check for
this by seeing if the tty was set to /dev/ttyv0.  This was useful for disting-
uishing whether or not one was remotely logged in or not, in order to bring
up other windows, etc.  Now we use 'xdm' and ttyp0 is taken on a "first come
first serve basis".  So how can one's login shell now know whether the
logging in is from the console or not?

2)	XPutImage though greatly fixed seems to leave holes on expose events
but only when refreshing XYBitmaps on the QDSS display.  This did not happen
before, but the expose regions used to only shift horizontally.  Same code and
everything. We only have R3 on a Vax/GPX so I can't speak for other machines.

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

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

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.

Otherwise, three cheers for the X Consortium!!

Philip Thompson (phils@athena.mit.edu)
Dept. of Architecture and Planning.