Just like in my previous post I need to jot down some useful commands for Lldb because I need to look them up so often. It contains standard breakpoint handling and running - just the very simple basics I should never forget. Note that this document will grow over time, hopefully.

First of all, do not forget to prepend xcrun to lldb, that makes it much more useable:

Since I happen to forget this every once in a while and end up in trying to debug in the command line but no symbols and no source is found, I drop a message for my future me:

Often I found myself starting an extra vimdiff session while I am actually working in another vim session. Finally, I took the time to search for a solution and I came up with the following two lines in my .vimrc:

After my last trials with OmniCppComplete, exuberant-ctags, and similar vim plugins or packages I was really reluctant to restart this endeavor again and again with disappointment in the end.

While IDEs like Eclipse, Visual Studio, and XCode were getting stronger, my vim usage has degraded to plain text and short task single file editing where fewer magic was sufficient and the universal powers of vim most appropriate. Even then, I was often drawn to editors like Sublime Text 2 due to features like multi cursor and plugins like emmet.

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.

Since my current job forces me to work on Windows most of the time, I desperately tried to get any shell/terminal on Windows shell to the same level as all other *nix shells in the 20th century. It turned out to be an endeavour but with a decently working bash in the end.

While working with unfamiliar and large svn trees I was wondering how I can get all svn externals within the source tree on the command line. As almost always, stackoverflow has the answer:

svn pg svn:externals -R

That’s it again and cheers!
iss

Today I had to check in into CVS after millions of years having passed since I last invoked cvs in a terminal. I was really surprised how much I forgot about the tool I was using on a daily basis, several million years ago. As I converted towards using Git mostly and need to use SVN occasionally I decided to make my own little SCM Matrix here, to remember just the basics. Of course, CVS, SVN, and Git work completely different and creating a repository in CVS has very little in common with creating a repository in Git.

As I need to call Matlab scripts from the command, e. g., for running Matlab scripts in a batch, every once in a while, I post a little reminder for my self here. Keep in mind that the called Matlab command needs to have an exit at the end, otherwise Matlab will keep running, waiting for input.

This is a follow up post of a previous one just using Matlab instead of Python. In the following paragraphs, I will show my way of reading and writing CSV files using Matlab. If you happen to know a better or more elegant solution, please drop a comment!