The adventures in LaTeX-land continues. Rikard didn’t want any page number displayed on the table of contents page, and after having tried a couple of different variants of \pagestyle{empty} and the likes we realized that for some reason that won’t work at all in the book-class. \pagenumbering{gobble}, however, seems to work in every class, but NOT inside the actual document (so I guess this means after having issued the first \chapter or \section command).

For the interested, I found the answer by searching and finding this post, which in turn lead me here.

RSS for logging purposes

I am toying with the idea of writing a small daemon which would create an RSS feed (or Atom or whatever is popular today, I don’t care) which I could then plug into feed2imap which I have on the server.

The idea then would be that I could write small monitoring scripts for whatever I wanted, check the temperature, check space on the disks, whatever, and have fcron execute these scripts every now and then, and the result of these scripts would be fed into the RSS daemon.

I haven’t thought this through yet at any rate, but I quite like the idea. We’ll see what comes of it :)

Revisiting my old friend Django

Grégoire (or as we like to call him, greg) began working on a Django implementation of the myConf concept, and I am helping out as best I can with it.

There were some template bugs which made the template overly complex which I am currently trying to iron out, and mostly the problem seems to boil down to that the input data to the template is stored in a way which makes access in the template harder than necessary.

So I’m attempting splitting the data up further, and using dictionaries as the overall structure, which of course meant that I needed to find how to iterate over a dictionary in Django.

I admit that it was quite some time since I read the Django docs, and had I done so I would eventually have found the solution, but google, as usual, beat me to finding the solution somewhere else.

The relevant parts are:

{% for key, value in dictionary.items %}{{ value }}{% endfor %}


A non-intrusive (but javascript-required) approach to comment spam filtering. It’s probably a good solution, but I don’t like forcing users to activate javascript in their browser.

This is just plain frakking disgusting.

Interesting, and well-documented, approach to combating email spam.

Tags: , , , , , , , ,

2 Responses to “2011w33”

  1. Glad to hear you’ve fixed your LaTeX issue.

    I know I’m quite a sucker for the underdogs and have bugged you about them already in the past, but that’s a good example why I prefer ConTeXt over LaTeX. While LaTeX has some excellent presets, when you want to work outside that box, you’re fighting very hard against the torrent. In ConTeXt the exact opposite is true — the defaults are quite spartan, but it’s very easy to change any values and settings.

    Disclaimer: Although I’ve used both LaTeX and still use ConTeXt, I’m far from being an expert in any of them. I’m just a casual user with an itch to scratch.

    Merged your two comments as they seemed to be very related both contextually and chronologically, hope you don’t mind

  2. Patrik says:

    It actually wasn’t my issue per se, but until Rikard was done I couldn’t consider myself done either :)

    ConTeXt seems kindof interesting, I’ll have to look into this.

    Would you say that the ConTeXt wiki is the place to go to learn about it, or are there better resources somewhere else which you can recommend?

    I didn’t find it immediately obvious where I should go on the site to actually learn it (I eventually found http://wiki.contextgarden.net/Hello_world which almost scares me, a whole lot of syntax all at once, with no “easing into it”).

    Thank you for the tip, I have a feeling that once I have taken in this tool, I will be as happy with this recommendation as I am with fcron (thank you again for that) :D