Today I was working with a colleague and reasoned about some code over chat. We sent filename and line number frequently and I got the impression that this is another perfect candidate for automation.

After reading an article on quadpoint.org I have been configured my IRSSI irc client with a highlight window as suggested by the author. Since I am running IRSSI in a screen/tmux environment, I only need to restart it when my (virtual) machine has been restarted, which is rarely the case. However, after restart, the highlight window is rarely in the right place.

Today I installed clang_complete using Pathogen (i. e., I installed it as a submodule of my dotfiles git repository aka nesono-bin. I tried to be smart and went into the submodule’s directory and invoked make install. That nicely built the vimball and installed itself - but whenever I tried to open a cpp-file I got the following error:

A long while ago, I re-wrote the transfer stack for the shell in Python. The transfer stack is the counterpart to the directory dtack, which is known by the commands pushd, popd, and dirs. The corresponding tools of the transfer stack are pusht, popt, and transfers, all of which can be found in my github repository.

Again, as a reminder for myself I am posting a table of shell control & escape sequences to navigate and use a misconfigured, non-configured shell or just for bragging purposes.

This is actually just a copy of an article from ubuntu.com, but they tend to move things around and I like to have short search times. Apart from that, this works for FreeBSD and even for Windows (tested with Windows 7) as well. Sorry for this this blatant plagiarism, but it might be also to your advantage ;)

One more note: If you want to create a bootable USB stick to be used on a Mac/OS X, do not forget to format the stick with Disk Utility to HFS+ with a GUID partition table.

I just added a workaround for DAViCal with Apple’s Address Book application. Since my update to 10.7.4, I was no longer able to add a contact to the server and the card stopped the whole server communication to fail completely.

or how to get rid of:
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so

After I moved my ubuntu desktop to kubuntu, the gnome-keyring always was started at every login, asking for my password. Besides the fact, that gnome-keyring does not feel native when working on KDE, every time I invoked svn in the terminal, I saw the error message from the subtitle. The solution was pretty tedious to find, so I hope to save you and myself some time if this will happen again.

For doing native FreeBSD stuff, I decided to install FreeBSD besides an existing Ubuntu installation. However, the Grub settings did not turned out to be as easy as the installation process.

Some weeks ago I had to run a simulation for my research which has been very elaborate and involved externally invoked scripts on remote machines (so-called Wuchtbrummen). These external calls were dispatched by a central main script, that was running on my local PC. To avoid a complete SSH session setup and teardown every time a new call should be invoked on a Wuchtbrumme, I wanted to have a persistent SSH connection, where all subsequent commands can be tunneled through.