On Fri, Apr 07, 2006 at 05:03:46PM -0700, iv_AT_c-66-229-172-60.hsd1.ca.comcast.net wrote:
> thats because X is an event model layered ontop of STDIN and STDout which
> amazingly are everywhere in UNIX. and IN X it actually intercepts these that
> is why you have 2 keybinding places.. because if you are focused on an xterm
> then the keybindings go there and always to X, and if you are on a GUI
> window they are mapped to whatever the library system for that GUI does...
> So yes it is a pain in the ARSE... I would think that the whole event model
> should be reorganized in another application layer so that new code base can
> deal with it in a organized fashion and not by hit and miss or my gosh I am
> not focused right and I press Xyz and deleted that... SHIT... not good...
> I would vote for some type of visual or bell feedback so that if you are
> doing something you get a hint that all is well before you rm -rf the root
> drive with a key binding short cut....
The main problem of X is, that it has not been revised at a time
when there have been chances to fix it. Now, there exist
thousands of X clients which depend on the broken X design (even
wmii). And this time the userland forbids to fix X by revolution.
The only road away from X works like XDarwin. Make X as a
frontend to some new window system which also fixes the mistakes
in Windows, OSX and rio. Actually I'd like to see a real rio
port to Unix.
Regards,
-- Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361Received on Mon Apr 10 2006 - 09:40:38 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 16:02:05 UTC