If you’ve not been following along, you might have missed it: it appears to me that even today, in 2011, mail systems work much better when setup the old way. Meaning with a local MTA for outgoing mail. With some niceties, such as sender dependent relayhost maps. That’s why I needed M-x mailq to display the mail queue and have some easy shortcuts in order to operate it (mainly f runs the command mailq-mode-flush, but per site and per id delivery are useful too).
It’s been a week since the last commits in the el-get repository, and those were all about fixing and adding recipes, and about notifications. Nothing like core plumbing you see. Also, 0.9 was released on 2010-08-24 and felt pretty complete already, then received lots of improvements. It’s high time to cross the line and call it 1.0! Now existing users will certainly just be moderatly happy to see the tool reach that version number, depending whether they think more about the bugs they want to see fixed (ftp is supported, only called http) and the new features they want to see in ( info documentation) or more about what el-get does for them already today…
Nowadays, most people would think that email is something simple, you just setup your preferred client (that’s called a MUA) with some information such as the smtp host you want it to talk to (that’s call a MTA and this one is your relayhost). Then there’s all the receiving mails part, and that’s smtp again on the server side. Then there’s how to get those mail, read them, flag them, manage them, and that’s better served by IMAP.
I wanted to play with the idea of using the whole keyboard for my switch-window utility, but wondered how to get those keys in the right order and all. Finally found quail-keyboard-layout which seems to exists for such uses, as you can see: (loop with layout = (split-string quail-keyboard-layout "") for row from 1 to 4 collect (loop for col from 1 to 12 ("q" "w" "e" "r" "t" "y" "u" "i" "o" "p" "[" "]") ("a" "s" "d" "f" "g" "h" "j" "k" "l" ";" "'" "\\") ("z" "x" "c" "v" "b" "n" "m" "," ".
Yes, that’s another el-get related entry. It seems to take a lot of my attention these days. After having setup the git repository so that you can update el-get from within itself (so that it’s self-contained), the next logical step is providing recipes. By that I mean that el-get-sources entries will certainly look a lot alike between a user and another. Let’s take the el-get entry itself: (:name el-get :type git :url "git://github.