Re: Eliminating the xterm
Re: Eliminating the xterm
- Subject: Re: Eliminating the xterm
- From: "Nathaniel Gray" <email@hidden>
- Date: Sat, 10 Nov 2007 12:11:38 -0800
On Nov 10, 2007 5:51 AM, Ben Byer <email@hidden> wrote:
> Ironically, the reason I chose to make xterm the default app for the
> X11 launcher was specifically so that there *would* be a user-visible
> result to running X11.app (aside from the icon, of course). We were
> worried that people would be accustomed to double-clicking on /Apps/
> Utils/X11.app in Tiger and having an xterm pop up (via the system
> xinitrc), and that if that didn't happen with Leopard, they'd think it
> was "broken". Oh, how silly that seems now...
I can understand your reasoning, and I agree that it's nice to have a
visible result from starting X for newbies. I'd say it's another
> I am a little confused, though, as to why we are trying to find a way
> to preemptively launch the X server without starting a "real
> program". Is this to avoid the .xinitrc / .Xresources race condition?
I posted that mostly because some people seem disturbed by the new way
and I just wanted to point out that the old way is still there.
The X resource problem is real, though. I can change my NEdit wrapper
to do "/usr/X11/lib/X11/xinit && nedit" but I can't just launch
"nedit" from Terminal.app because I have a lot of customization in
.Xresources. Isn't there a way to get the X server to handle its
initialization before it takes events from the launchd socket?
> As for cut and paste -- oh, the fun we've had with cut and paste. Cut
> and paste sucks in X11.app. Why?
> 1. Cut and paste kinda sucks in X11 in general, and this is a
> generally agreed-upon fact in the X community. Yes, it generally
> works, but it's unpredictable at best. There have been murmurings
> about trying to fix that across-the-board -- and I'm first in line
> when it comes to spearheading that -- but for whatever reason, it
> still hasn't happened.
> 2. About half of the different permutations of cut and paste between
> X11 and Aqua are "simple", in the sense that it's obvious what we want
> to accomplish. Many of the rest are open to debate.
> 3. Most of the cut and paste magic happens within closed-source code
> -- quartz-wm (hence the need for running 'quartz-wm --only-proxy).
> This is stupid.
YES!
> The source for those bits of code is now up here -- https://bugs.freedesktop.org/show_bug.cgi?id=13066
> . Someone *please* help me find a way to get this into the server (or
> at least X11.app in general) so that we can together work on it.
zomg! I'll take a look, but I don't have much free time these days.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden