Skip to main content

Welcome LiLA!

Hamburg, April 2006. A few guys, a bar, and liters of cheap water. Right, it's all about Common Lisp.

I was attending ECLM06 and with me more Austrians than anticipated. After a quick hello, the idea was clear. We need to plan a strategy for the subversive infection of our fellow countrymen with the fruits of the theoretic work around the Lambda Calculus: Lisp!

After the regular phase of idleness, and occasional real life contact, I came up with the cute name LiLA, for Lisp Lovers Austria. But the name was found to be revealing on our true nature, and "Lovers" was substituted by the more neutral word "Lab" (thanks for the suggestion Patrik!). <Add more idleness here>, and right after that lisplab.at went online!

Our name, Lisp Lab, also fits neatly with a project we are associated with: metalab. metalab is an open center in the heart of Vienna, providing us with space and infrastructure for our meeting and events.

Talking of events, there will be Common Lisp Introduction workshop in metalab soon. I'm aiming to hold a two hour workshop consisting of 45 minutes talk, break and one hour hacking on your game-theorically perfect tic-tac-toe implementation. For the latter, we can also go for a more stupid computer player, otherwise playing and knowing the game will end in a draw is no fun.

Watch this site for a date/place announcement of the CL intro.

Comments

Popular posts from this blog

Liskell standalone

Some time has passed since I last blogged about Liskell. It is not dead nor have I changed my mind that Haskell needs a proper meta-programming facility not to mention a better syntax.Liskell was a branch of GHC once. Now it sits on top of the GHC API, or I should rather say sneaks behind its back as it creates its own API as the original one is not suitable for the stunts I'm interested in. If Liskell sticks with GHC as its soil, I will definitely send patches upstream to refine the GHC API in the areas where it needs more flexibility for Liskell. However for the moment, my main target was to get something out that compiles with a stable version of GHC.You can grab it with the usual: darcs get http://code.haskell.org/liskell/ This version has been tested with ghc 6.10.1 and should install like: ./Setup.lhs configure ./Setup.lhs build ./Setup.lhs install cd LskPrelude make install-inplace Optionally you can run make tests in the testsuite subdirectory. Thanks to community.haskell…

XMonad GridSelect

Personally, I not just need a window manager, I need a focus manager. I tend to think of windows as TODO items, and as there are many TODOs in life there are many windows on my workspaces. Usually a fraction of that can't be closed or worked on immediately, so they linger around on my desktop, cluttering my workspace.I used to use the Tabbed layout. But Tabbed isn't the answer when you are a guy who reports bugs such as "XMonad 0.6 with Tabbed dies when firefox-session-restore slams 40 windows at once on the desktop". In other words, I use a lot of windows. The workspaces concept isn't particularly useful to me either. My mind just doesn't work with mental boxes. So the result is, that I have too few workspaces with too much windows on them, so that Tabbed has trouble displaying useful window titles, and navigating through them is slow and cumbersome (mostly because tab switching generates a lot of useless X Expose events).GridSelect is my answer to that. It…

Removing CHS based access from windows boot loaders

Recently, I had troubles to migrate my Windows installation from VMWare to VirtualBox. When booting the vmware created partition in virtualbox, I got "NTLDR not found". So I sharpened the knives and got down to business with vmware's gdb interface and virtualbox's internal debugger. Tracing the execution showed that the BIOSes of the two products reported different geometries on the INT 13h interface. The generic method contained in the boot loader to read a sector from disk is "clever" as it checks whether the sector is below the maximum sector index that is reachable with the CHS geometry reported by the BIOS. If not, it uses the LBA interface of the BIOS. If yes, the cleverness of the boot loader suddenly vanishes. Instead of using the BIOS reported geometry to break the absolute sector down into its CHS components, the boot loader uses a geometry stored in the so called BIOS parameter block. That's a section of the first sector embedded into the boo…