Skip to main content

#cl-gardeners: a channel for Lisp newcomers!

#lisp on FreeNode is home for many experienced CL wizard, and not primarily a place for asking trivial lisp newcomer questions. Of course, not all of these questions are valid. Some of those people joining #lisp simply want to get their homework done (preferably by others). But sometimes there are people that seriously want to learn Lisp. Every single one that is not sucked into the Common Lisp community is a loss that might not be quantified. And selfish as I am, I simply dislike the idea that there are any obstacles for lisp newcomers to start writing lisp code that someday I might be able to use :).

Now we have a channel, where newcomers can ask question and eventually get answer by newcomers. It is #cl-gardeners. You don't have to fortuneteller to predict that sometimes newbies can answer questions by other newbies better than an experienced CL. And in most cases, both parties gain knowledge. The unexperienced newbie by getting an answer, the semi-experienced newbie by repeating his partially acquired knowledge; you'll find that learning technique in every serious "teachers handbook".

However, CL wizards that are in a mood for providing help to newcomers are invited to join #cl-gardeners to share their experience. This gives #lisp the opportunity to send help seekers to #cl-gardeners when #lisp is busy with more important stuff or simply doesn't want to give an answer. (This is also the reason why #cl-gardeners should be on the same net as #lisp.)

So, if you are interested join #cl-gardeners on FreeNode. Lurking and idling is totally ok, and actually desired. Please consider #cl-gardeners as candidate for your autojoin list.

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…