: ) wonderful world ( :

After a very close relationship with a Koss The Plug one I came over. My new buddy is a Sennheiser CX300-S, which is like this:

Which is crazy because I feel high sounds more intense. Other attributes are:

Ettan.

Determine how many source line is presented under the current directory:

( echo 0 && find -name “*.lisp” -exec wc -l ‘{}’ ‘;’ | cut -d’ ‘ -f1 | sed -e ’s/$/ +/’ && echo p ) | dc

As I’ve already been to hunchentoot land, and that kind of web programming isn’t that easy, I decided to travel to the kingdom of ucw. I managed to start the server by just loading start.lisp file. Afterwards I felt the need to connect to its slime server as it is shown by the introductory hello-world.mov movie (*the link is broken, but I have it somewhere on a DVD, will upload it soon*). The case is, that video is out of date and start.lisp (the easy way to become able to benefit from this all) doesn’t start slime for you. One has to call explicitly ucw:start-swank in the REPL remaining after start.lisp. This required hard work, I had to perform several greps to find out who and when calls swank:create-server. Finally every piece of information started serving me later on this tutorial movie. Oh, there’s a second good to know thingy here, render-on doesn’t exist any more, use render instead.

Some kind of high level overview of ucw’s terms as far as I understood. Components are entities encapsulating all the pieces you want to use from the point of view of a web page. One has to defmethod render methods, which are projections of components to the space of HTML (note definition of projection here). Actions can modify components and redirect the flow to them. (AFAIK)

Deep stuff man.

I’m happy to introduce you cl-bf @ sourceforge.

cvs -d:pserver:anonymous@cl-bf.cvs.sourceforge.net:/cvsroot/cl-bf login
cvs -z3 -d:pserver:anonymous@cl-bf.cvs.sourceforge.net:/cvsroot/cl-bf co -d my-cl-bf trunk

afroid-laptop% tla make-log
/home/kotee/tla/my-cl-bf/++log.cl-bf--mainline--0.1--kotee@elte.hu--cl
afroid-laptop% vim ./++log.cl-bf--mainline--0.1--kotee@elte.hu--cl
afroid-laptop% cat ++log.cl-bf--mainline--0.1--kotee@elte.hu--cl
Summary: add readme
Keywords: 

Info about installation, etc.
afroid-laptop% echo > readme.txt
afroid-laptop% tla add-id readme.txt
afroid-laptop% tla commit
A  .arch-ids/readme.txt.id
A  readme.txt
* update pristine tree (kotee@elte.hu--cl/cl-bf--mainline--0.1--patch-2 => cl-bf
--mainline--0.1--patch-3)
* committed kotee@elte.hu--cl/cl-bf--mainline--0.1--patch-3
afroid-laptop%

Tre Ankare.

I’d like to emphasize that the code itself isn’t fully functional. Yet here is the way how to check it out with GNU arch. I used a clean fresh new user and with that:

temp@afroid-laptop:~$ tla my-id
arch: no arch user id set
temp@afroid-laptop:~$ tla my-id "Szabolcs Szucs <kotee@elte.hu>"
temp@afroid-laptop:~$ tla my-id
Szabolcs Szucs <kotee@elte.hu>
temp@afroid-laptop:~$ tla register-archive kotee@elte.hu--cl \
> http://people.inf.elte.hu/szucssza/archives/
temp@afroid-laptop:~$ tla archives
kotee@elte.hu--cl
    http://people.inf.elte.hu/szucssza/archives/
temp@afroid-laptop:~$ tla my-default-archive
my-default-archive: no default archive
temp@afroid-laptop:~$ tla my-default-archive kotee@elte.hu--cl
temp@afroid-laptop:~$ tla my-default-archive
kotee@elte.hu--cl
temp@afroid-laptop:~$ tla categories
cl-bf
temp@afroid-laptop:~$ tla branches cl-bf
cl-bf--mainline
temp@afroid-laptop:~$ tla versions cl-bf--mainline
cl-bf--mainline--0.1
temp@afroid-laptop:~$ tla revisions cl-bf--mainline--0.1
base-0
patch-1
temp@afroid-laptop:~$ tla get cl-bf--mainline--0.1 my-cl-bf
* from import revision: kotee@elte.hu--cl/cl-bf--mainline--0.1--base-0
* patching for revision: kotee@elte.hu--cl/cl-bf--mainline--0.1--patch-1
* making pristine copy
* tree version set kotee@elte.hu--cl/cl-bf--mainline--0.1
temp@afroid-laptop:~$ cd my-cl-bf/
temp@afroid-laptop:~/my-cl-bf$ ls
{arch}  bf-inter.lisp  bf-low.lisp  bf-strip.lisp
temp@afroid-laptop:~/my-cl-bf$

temp@afroid-laptop:~/tla$ ls
temp@afroid-laptop:~/tla$ tla register-archive kotee@elte.hu--cl-SOURCE \
> http://people.inf.elte.hu/szucssza/archives/
temp@afroid-laptop:~/tla$ tla archives
kotee@elte.hu--cl-SOURCE
    http://people.inf.elte.hu/szucssza/archives/
temp@afroid-laptop:~/tla$ tla make-archive --mirror-from  \
> kotee@elte.hu--cl-SOURCE ./cl-bf/
temp@afroid-laptop:~/tla$ tla archives
kotee@elte.hu--cl
    ./cl-bf/
kotee@elte.hu--cl-SOURCE
    http://people.inf.elte.hu/szucssza/archives/
temp@afroid-laptop:~/tla$ tla archive-mirror kotee@elte.hu--cl
* mirroring kotee@elte.hu--cl-SOURCE to kotee@elte.hu--cl with limit (null)
* creating version kotee@elte.hu--cl/cl-bf--mainline--0.1
** adding revision cl-bf--mainline--0.1--base-0
** adding revision cl-bf--mainline--0.1--patch-1
temp@afroid-laptop:~/tla$ find
.
./cl-bf
./cl-bf/=meta-info
./cl-bf/=meta-info/name
./cl-bf/=meta-info/mirror
./cl-bf/.archive-version
./cl-bf/cl-bf--mainline--0.1
./cl-bf/cl-bf--mainline--0.1/base-0
./cl-bf/cl-bf--mainline--0.1/base-0/log
./cl-bf/cl-bf--mainline--0.1/base-0/cl-bf--mainline--0.1--base-0.src.tar.gz
./cl-bf/cl-bf--mainline--0.1/base-0/checksum
./cl-bf/cl-bf--mainline--0.1/patch-1
./cl-bf/cl-bf--mainline--0.1/patch-1/log
./cl-bf/cl-bf--mainline--0.1/patch-1/cl-bf--mainline--0.1--patch-1.patches.tar.gz
./cl-bf/cl-bf--mainline--0.1/patch-1/checksum
./cl-bf/cl-bf--mainline--0.1/patch-1/++revision-lock
./cl-bf/cl-bf--mainline--0.1/patch-1/++revision-lock/+contents
temp@afroid-laptop:~/tla$