If you get an error updating cliki, this is intentional. I've
temporarily set it read-only, due to the actions of some pubescent
wannabee who replaced upwards of twenty pages with pornographic
images. Will reenable it as soon as something shiny distracts him and
he pisses off elsewhere.
The good news is that apparently there is no bone damage in my
shoulder (got it x-rayed today). The bad news is that even soft
tissue damage may take 6-8 weeks to heal, and in the meantime every
time I raise my arm above shoulder I get a stab of pain the likes of
which I wouldn't wish on anyone except possibly wiki vandals. So not,
really, in a very good mood.
Finally installed various random CLiki fixes on www.cliki.net,
allowing me to shorten the bug list to something like 30% of what it
was. New downloadable version imminentish, but I'm going home first.
Bcc: dan
To: lispweb@red-bean.com
Subject: ANN: CLiki 0.4.3
X-Draft-From: ("nnml+private:mail.lists.london" 3116)
From: Daniel Barlow
-text follows this line-
CLiki 0.4.3 is now in cCLan. This is approximately the version that's
been running on www.cliki.net for the past few months.
New in CLiki 0.4.3
Versioning! At the expense of making the file names correspond even
less closely with the page title, we now produce a version per edit.
While indexing we collect the first sentence of each page, and
make it accessible as (CLIKI-FIRST-SENTENCE page)
Legacy searches now print this out.
Beginning of the long slow process to separate generic cliki engine
stuff from www.cliki.net stuff: new cliki-net class that you
probably don't want to use unless you're me
Indexing tweaks mean startup on big clikis may be a bit faster.
Bug fixes: RSS generation, topic searches.
(Uncategorized) marker added to default text for new pages.
Note that there is also an internals change which you may run into if
you are building cliki-based tools: to make backlink searches and
updating simpler, CLIKI-PAGE objects are now created when references
to non-existent pages are encountered during indexing. These
placeholder pages have NIL :pathname and :versions slots.
(You can see this behaviour in action at http://www.cliki.net/Dan%20Moniz,
at lease until/unless someone creates that page)
This means that if you want to detect whether a page /really/ exists,
you should not just rely on find-page returning NIL, but also
test the pathname slot.
I'm daydreaming. Yesterday I somehow ended up resubscribed to
comp.lang.lisp, to participate (well, mostly laugh at) in the
"Modernizing Common Lisp" thread. (My fingers seem determined to type
that as "Mordorizing"; read into that what you will). Fortunately now
I'm not taking it as seriously I find it more entertaining than
frustrating. I'm not going to post some long screed about it here,
but I did start thinking at a tangent.
Adopting a Nick Hornby writing cliché (which I'm sure he
stole from the Mail on Sunday magazine anyway), here are my top five
asdf-install-compatible libraries (excluding the ones I wrote). These
are not in order of merit, just in the order they occur to me.
xmls: I think I'm only using this for xml generation rather than
actual parsing, but it's a snap for all those trivial XML formats like
RSS.
cl-ppcre: on which topic I have written before, yes.
pg: although the version I'm actually using predates its
asdf-installability (it works, and it's in production, and so I'm
naturally reluctant to upgrade it).
split-sequence: ok, really, how can I not?
clx: kind of stretching a point here in that I asdfized it and
host the cvs repository, but the hard work is/was all done by
other people.
The common feature in all of these (except CLX, which I stuck in
simply because so much else depends on it) is that they're small, do
one thing well, and don't impose their way of working on me.
Remember, you get ten points for a library, but only two for a
framework.
In other news, I read somewhere that the Allegro CL 7.0 beta now
includes asdf. I don't know if beta programme participants are bound
by NDA or anything, but just in case they are I've conveniently
forgotten where I got this news.
A brief note on diff and CL, for people who write functions with more#
My shoulder is more or less better. The bruising is still pretty
evident, and it still aches a bit, but I can drink right-handed again,
which is the main thing.
Club Blue Room, take
a bow. I think I spent about eight pounds in there (new heel brake,
small tube of bearing grease) since I bought my skates three years
ago; almost every time I go back to spend money on something else they
tell me I don't need it and how to fix the problem anyway. At least,
they suggested cutting up bits of old insole to move the position of
my ankle bone in the skate boot; I creatively interpreted the
instruction and cut up an old mouse mat instead - I seem to have more
of them lying around than spare insoles, for some reason. Foot much
more comfortable now, anyway. Oh, and thanks to the
for the mousemat too - but don't worry, guys, I haven't found a
similar use for the wooden giraffes yet.
I found today what seems to be the only arm movement that still makes
my shoulder hurt: pumping bicycle tyres. What's interesting, though,
is that (a few hours later) both of my shoulders now ache, not just
the right one. I'm probably carrying my neck in a funny way to avoid
pulling something, and thereby stretching something else. Or
something. That's handwaving, albeit fairly cautious handwaving in
case I set something else off.
Araneida 0.85 is out. Its release received almost no publicity,
because to be honest there wasn't much new in it. The next release of
Araneida, however, is rumoured to include support for
OpenMCL and Allegro (and possibly also, it's rumoured, ABCL). At least,
I've given Brian CVS commit access, so I hope it will :-)
Why is there apparently no open source icalendar server? My
conjecture is that the specification is in some way stupidly complex.
So, what about subsetting it? My mobile phone claims to understand
either icalendar or vcalendar (I forget which); if they can build
calendaring into such a terminally dumb device as that, surely it's
not impossible to do a reasonable subsetted implementation of
icalendar as open source, then rely on network effects to make it a
universal pidgin. But what's an appropriate subset?
Apparently there's a bug in my diary-publishing code which only#
Tue Jun 1 18:30:27 2004
Topics:
Apparently there's a bug in my diary-publishing code which only
exhibits when there are no entries in a given month.
This
is more in the nature of a workaround than a fix