Posts

  • Delicious bookmarks search in the shell

    fil.tero.us is no more, long live filterous (Update: Unfortunately both sites are long gone. Sorry for the inconvenience!)! After much deliberation (and switching to a more productive platform & programming language), I decided to re-implement the Delicious personal bookmarks search page in Python for the *nix shell. The result is more security (I don't store your bookmarks for you), more uptime, and more opportunity for parsing with shell tools such as less, wc, sort and grep.

  • Move file between git branches

    For my own memory more than anything else:

  • Guest uploader setup script

    Just slammed together a script to add users and give them access to the "upload" user directory.

  • fgit - Run a Git command in several repositories

    fgit enables you to run a Git command in several repositories with one command. For example:

  • Query CERN LDAP from the shell

    Here's one for the shell nuts:

  • Howto: Timelapse video from photos

    It's amazing what shell tools can do: Flickr accepts HD video (720p, or max 1280×720) up to 30 FPS, so I tried to create one within those limits from the high resolution photos from today's sunrise. Turns out to be incredibly easy with free tools on Linux:

  • Use SVG in SchemaSpy

    SchemaSpy PNG images take a lot more space than their equivalent SVG counterparts. To replace the PNG images with SVG you can use schemaspy2svg (Bash and DOS batch scripts).

  • EIF replies

    In response to Glyn Moody's Open Source and Open Standards under Threat in Europe (Update: sorry, the link is dead), here are the open replies to the key people (I'll post as they are sent).

  • Automatic backups to remote machine

    Update: SSH public key authentication isn't supported on the system I want to backup to, so I've changed the procedure to create a cron job on the server instead of the client.

  • BASH / Bourne Shell which outputs its own documentation

    I love Python docstrings - It's a great application of the DRY principle. The excellent Advanced Bash-Scripting Guide has an example which does something similar, but it embeds the documentation in a variable in the middle of the code. This makes it less readable and findable than ordinary comments, and leads to duplication if you want to have the same documentation as a comment for other developers. Here's a very simple solution, which I'm sure can be improved to fit your documentation style. It simply prints all non-empty lines from the start of the file: