In the spirit of the balloons: e, the balloon cause it’s cool like that.

There’s also an updated version of the ri search here

Two thumbs up for ‘e’.

How hard would it be to change dwm to produce a ruby extension ?

dwms goal is not to have extensions – all configuration is done before compiling :)

Who cares about dwm’s goals ? I care about ruby :-p

I am going to write a window manager whose goal is not to have configuration. All extension is done before compiling (by writing code). Also it will be written in Intercal for purity.

Why do you choose Intercal ? I prefer whitespace.

mentalguy: sounds like dwm:

dwm is customized through editing its source code, that makes it extremely fast and secure – it does not process any input data which hasn’t been known at compile time, except window title names and status text read from standard input.

No, see, reading arbitrary status text from standard input is definitely a security hole. Also, can you say “bloat”? I can. Window managers don’t need to read anything from standard input or display arbitrary status text. They are for managing windows.

Also, window titles. Accepting arbitrary window titles can lead to all kinds of badness. Who knows what some malicious program might put in there?? Besides, you really only need one window title: “xterm”. If you decide you really want additional window titles, it is a simple matter of adding them in the source code.

Lastly, I have chosen Intercal because it has built-in support for the Observer pattern via the COME FROM construct. This is helpful for event-based programming (like you need to do for window managers).

One more thing—I will not be releasing the source code or the compiled program, or telling you its name. This will do a better job of maintaining a small and elitist userbase, preventing n00bs with stupid questions. If you would like to use or customize my window manager, just recreate it from its description in this post.

MenTaLguY: Running a window manager is a massive security hole and I can’t believe that you’re recommending it to these whom I call my friends. I find myself at once infuriated, agape, unvested, empuffed and pentessentially swept into delorium that you would dare encroach upon the standards of this blog and mislead the readers of it. ( AMONG WHICH YOU ARE COUNTED !!) Please, let’s not go there ever again. I feel like I’ve come home to find the mansion absolutely frigid, my skin whelming with goosemarks, only to find that EVERY LAST WINDOW HAS BEEN LEFT AJAR . I just cannot suffer the last of those loosened shutters.

Window managers occupy the space of and encourage the presence of a monitor, which itself is an unsecured hole through which intruders may peer. Multiple monitors are a series of holes, a captor may choose to exit from a different one than was used to enter. Monitors unending is an obvious leak, a sign of hacked reality, which quickly leads to a counter overflow exploit. These are the fundamentals of cryptoreal (“meat hat”) security, which I need not belabor with details.

Serial ports, PCMCIA slots, RJ-45 jacks, these are the holes that meat packets can enter and cause cryptorealogismic overloads. While, traditionally, bandits have use fingers, most have protected their digits from counterintrustion measures (embedded guillotines, 24-pin microguns, salts, etc.) by fashioning new meat fingers from pork sausage sculpted over fiber optics and those stratus clouds formed in the intersection between abundant wifi signals. It is pentamount that such connectors and ports be lasered off or stacked with secure non-hole steel booting.

ROFL ! Yeah, this one time I tried a GUI web-browser and it was all changing the title-bar every time I loaded a page! And I had to use the mouse! Needless to say I went back to lynx immediately.

But _why… what if the attackers lurked waiting in your CPU like oh so many tiny little people in a TrojanHorse? Waiting for you to turn you computer on before leap out with insideous intent.

We must certainly machine the raw components of our processing engines from the raw ore of the earth, otherwise who knows what secrets lie within it!

What is all this “web browsing”? Insecure protocols have been the cause of every known security breach to date. I am always sure never to touch things like “ports” and “sockets”. Instead, I use my network card to handcraft packets made of random collections of bits, which I then hurl out into the internet with great abandon. In fact, that’s how this post was written.

adam: I await this new EarthenCore PC with a stony semblance, awash with topaz stolidity. (Unless, of course, you count that shit-eating grin of mine.) I didn’t buy this indian clay XT case for nothin!

SargeantCircles: SIGH! I shouldn’t have to coach you on the indelicacies of handling your network card directly with your own meaty God-given device drivers! TWENTY DEMERITS !

Meaty devices,
Embrace fertile cryptoreals,
Of hardened kernels

Abundant wifi,
Ubiquitous encroachment,
Pentamount captors

An obvious leak,
Sign of hacked reality
the mansion frigid

(17th century kaiku describing MentalGuy’s new WM)

On a more serious note, anyone seen Kaze ha kase? It has a built-in ruby sandbox console (albeit nowhere near as ambitious or freaky-freaky as why’s—more like a simple REPL ) with autocompletion and command history. I haven’t figured out if the browser innerds or the DOM is exposed in any way, or if external scripts can be loaded automatically (manual require appears to work fine), but it looks pretty neat. You need to pull the CVS and enable the expert UI level (under View menu), then the ruby console will be available under Tools -> Extension -> ruby dialog.

MonkeeSage Its UI looks kind of clunky, but how can you go wrong with built in ruby scripting support :)

I personally intend on running it off my hand made Ruby Encrusted Earth PC, now I just need to find seven monks who have sworn vows of silence to seal and bless it before I let it ingest these ‘protocols’.

Druids, definitely.

Druids sacrificing yaminals…