2014-11-25 More old mails, I go for, these days. Today, it were mmh mails. Not so old is Sime Ramov's bug when sending mails with BCC headers on a OpenBSD machine with opensmtpd. I don't really understand the bug, yet. Today, I had to realize, that I no longer have exactly one git setup (username and email address) but two. In earlier days, ei- ther git was configured on the machine, then it was for my normal email address, or it was not, then git failed on committing. This is no longer the case. Someone showed me how to use the changes tracking feature in Mi- crosoft Word and how to compare and merge files. I was able to work sufficiently well with it. Of course, editing text this way is limited compared to editing in vi. The differences are two- fold: First, a lot of small things are annoying (fiddling with the mouse to select exactly what I want; the need to move the mouse large distances often; no powerful repeat-last-edit-command feature like `.' in vi) and second, the lack of a really powerful editing mode to be able to do large edit operations with one sin- gle command. But I don't want to criticize too much -- Microsoft Word has inproved -- just one more thought of general nature: All those functions that Microsoft Word offers with it's track changes facility are general version control functions. They have been implemented a hundred times in version control systems. Now, they are implemented anew in Microsoft Word. They will soon be implemented a next time in Microsoft Excel (or are they already present?) and then another time for Microsoft PowerPoint, and so on. On Unix, if you have one version control system, then you au- tomatically have its functions available to all programs, because their files are plain (readable) text and version control works on plain text. (Of course, you need to learn how to use it and how to read diffs and so on, but then you have learned it for everything you'll ever have to do with version control.) http://marmaro.de/lue/ markus schnalke