Log in

No account? Create an account
Previous Entry Share Next Entry
Tired, Window Manager Hacking
Didn't get to sleep until 2:30ish. Quite exhausted. Don't want to interact with children in order to prepare them for school. "Tough Shit", I know, but that doesn't preclude me from whining.

I did play with evilwm some more -- specifically, compiling it and setting it up in X on the mac. Unfortunately, the combination of three button emulation with modifier keys to drag things around and resize them does not work so well. I'm not actually sure of the issue, but I did hack the code to report mouse events, and found that that evilwm is never getting the 'middle click' event when it can be interpreted as a paste event. (So for xclock, it is getting through, but for xedit, where it can be interpreted as a paste, it's not.)

This could well be some kind of X configuration thing, or something else: Certainly OS X does not create the cleanest X config in the world. But I also don't have a lot of goal of futzing with X.

Oh, and booting to Ubuntu on the Macbook failed -- never even got past the loading, the progress meter just froze. I let it sit for 20 minutes, then gave up. I'm hopeful that I can eventually get most of what I need out of OS X -- possibly I'll still need to upgrade to Leopard to get some of it, since in Leopard, X is X.org instead of X.
Tags: , , ,

  • 1
(Deleted comment)
I did look at that page. Switching vttys didn't seem to do anything -- the whole thing just seemed 'stuck'. It being 12:30 AM, I didn't futz with it too much.

Using DarwinX11 (or at least, it's XDarwin.app) -- there is a key/mouse configuration options, but they seem to be totally ignored when I change them. Also, I'm not sure that it would matter, since I confirmed that it was getting the correct mousebutton when using the default key configurations (even though changing the configurations didn't work) -- it's just that when I used a mousebutton that could be interpreted as 'paste', it wasn't allowing me to modify that with an 'alt' to make it affect the window instead.

One thing that I'm happy with is how easy evilwm is to hack -- with the total source code only being 2000 lines, it's actually easier to get involved in what evilwm is doing than it is to get involved in a Javascript app like OpenLayers (which has a lot of convention, and even finding the right piece of code can be a pain in the butt). Hooray for super-simple window managers -- even if XDarwin gets a 'boo' for sucking.

(Deleted comment)
Nah. I bet this one is a problem with my hardware, not with the software, and until I do enough digging that I have a fix, it doens't make sense to report it. Other people -- i fact, the majority of the web reports I could find -- report that it works fine, so there's clearly something special in my case: without debugging it on my end, there's no way that anyone else will be able to get it fixed either.

  • 1