Blog - Everything

I tried some Trader Joe Tofu Spring Rolls, just for the heck of it. The tofu and peanut sauce tasted decent, but they completely screwed things up by including raw mint leaves in the roll. What a terrible idea. Mint belongs only in ice cream and gum, and even then, not in raw form. I had to wash the taste out of my mouth with a hot dog.

I had an idea for a new Emacs mode yesterday while talking with a coworker: a clipboard manager for Emacs. Think M-x browse-kill-ring, but able to pick up on yanks and kills made by other X programs, and set the current X (and Emacs) selection. An initial search didn't yield anything similar to this, so it might be interesting to implement — don't think I'll do it myself, though, since XFCE's Clipman is good enough for me.

Q: What do you get when you cross a mobster with an international standard?

A: You get someone who makes you an offer that you can't understand!

— /usr/games/fortune

Obligatory joke about OfficeOpen XML:

Q: What do you get when you cross Microsoft with an international standards organization?

A: You get an Office format that you can't understand.

Gmane is a handy way to follow mailing lists, especially those with a large volume of messages. There are cases when it is not a good idea to use it, however.

Maintainers of a project should definitely not use it to follow mailing lists for their projects. The same goes for active contributors. The reasons are as follows.

1. If your main computer breaks down and you have to rely on just websites, you would have to visit the Gmane web interface for each mailing list that you're a part of. This would mean you can't easily keep track of which messages have been seen, and becomes a hassle if you're involved in several projects.
2. More things can go wrong. Most people use something like leafnode to download messages from Gmane. I recently ran into a bug where leafnode was not fetching messages for any newsgroups (after about three weeks of being without internet access) until each newsgroup was visited and had all of its messages read. I just don't have time to investigate such things.
3. If your mailing list has a policy of sending replies both to individual senders and the list itself, this is nontrivial to do.

I've come up with my own way of preparing coffee. The goal is to make something that tastes decent, takes less than two minutes to prepare most mornings, and only occasionally requires brewing. This is similar to my earlier post on this topic, but with an improved formula.

Dependencies

Equipment

• Coffee-making apparatus. I use a cheap carafe and boil my own water.
• Refrigerator.
• Microwave.
• Coffee cup.
• 1-liter pitcher with lid.

Ingredients

• Medium-roast coffee blend.
• Espresso coffee.
• Milk.
• Real french vanilla liquid creamer.
• Filtered water.

Directions

Preparing a batch

1. Follow normal coffee-making directions, but with the following proportions. Make sure to place the medium-roast coffee into the coffee-making apparatus before adding the espresso coffee.
   • 5-6 cups of water
   • 1/4 cup of medium-roast coffee
   • 1/4 cup of espresso coffee
2. Let prepared coffee cool, and then pour into 1-liter container and store in refrigerator.

Preparing a single cup

1. Fill cup about 1/4 full of refrigerated coffee mixture.
2. Fill cup with milk to about 2/3 full.
3. Heat cup in microwave between 1 minute and 1.5 minutes, depending on desired temperature.
4. Add creamer to taste. I usually add around 3 teaspoons of it.

The resulting cup of coffee has a nice flavor from the scalded milk, and the espresso adds a much-needed note of authenticity.

I'm going to stop using PGP signatures in email messages that I send. While it can be satisfying to sign off on every email by entering a PGP passphrase, it is just not worth the effort anymore. Not enough other people use them, and many of those who don't use them get confused when they receive these messages, due to their email clients sucking.

I think that the next big thing in GUI apps should be the ability to take the exact contents of a window and send them to a remote machine. The use case for this is: you start an app at home, go to work, ssh (with X forwarding) into your home machine, and realize that you need to use that app again. Normally you'd kill the app and restart it. But what if you could just "clone" the window so that it appeared on your work machine, responsive to new input? I'd love to see functionality like this being added at the toolkit level (i.e. GTK, Qt) so that application developers would not have to do any work to activate it.

One of the nice things about running many apps in Emacs is that I already have that ability. I can just use the multi-tty support in Emacs 23 to open up either a terminal window or a new GTK frame, and then switch to the buffer that contains the app.