Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

rjbs (4671)

rjbs
  (email not shown publicly)
http://rjbs.manxome.org/
AOL IM: RicardoJBSignes (Add Buddy, Send Message)
Yahoo! ID: RicardoSignes (Add User, Send Message)

I'm a Perl coder living in Bethlehem, PA and working Philadelphia. I'm a philosopher and theologan by training, but I was shocked to learn upon my graduation that these skills don't have many associated careers. Now I write code.

Journal of rjbs (4671)

Sunday March 02, 2008
10:50 PM

more code for mutt on osx

[ #35820 ]

I have a fairly complicated mutt configuration. It could probably do with more streamlining, but it's pretty easy for me to update, because of the way I generate it.

Some of it, of course, comes from Addex. That's only some of it, though. Namely, the folder hooks, folder subscriptions, and a lot of the aliases. That leaves a lot of things unconfigured: default headers, folder names and locations, connection methods, helper programs (i.e., the mailcap), OpenPGP and S/MIME config, keybindings, colors, and all sorts of other little things.

A lot of these I really do want to set myself, once, by hand. I want the same basic colors everywhere, for example. A lot of other things vary from host to host. On the server to which mail mail is delivered, my mail is laid out in Courier-style Maildirs, so my inbox is in ~/Maildir/{cur,new,tmp} and one of my folders is ~/Maildir/cpan/{cur,new,tmp} and so on. On my laptop, where I sync that mail with OfflineIMAP, I end up with my inbox in ~/Maildir/INBOX/{cur,new,tmp}. Some folders are renamed, others are omitted. That affects save hooks, folder hooks, folder subscriptions, and other settings.

At work, I have an entirely different set of folders, as well as a different From header, a different sig, and other different settings. On all my machines, I have different helper applications. On my workstation at work, which I use only via ssh, I can't open images. On my laptop, I need to use a wrapper around Preview.app. Elsewhere, I might want to use Firefox. On some machines, I want HTML rendered with lynx, and if there's no lynx, html2text will do, and so on.

So, a lot of my mutt configuration is generated for me by little programs, either when I run mutt or when I deploy its configuration to my homedir from a git checkout.

Since it's important to know what machine I'm running on, I have a module called WhichConfig. It exports a routine, which_config that tells me what configuration to use. For the most part, this is either a hostname or "default." It works like this:

  1. if the hostname is a known hostname, use that config
  2. if we find a known string in ifconfig, use the associated config
  3. use default config

The ifconfig check is pretty crude, but very, very effective. I look for the MAC address on hosts for which I control the hardware and IP address on hosts that I don't. It's easy to change the way the test works, but so far this has always worked. Many of the rest of my tools rely on WhichConfig.

The first application is simple; my muttrc contains this line:

source `~/.mutt/which-config`

which-config just prints out a filename based on the appropriate config. That file contains settings that I just want to set by hand on each host.

A more interesting (but still very simple) helper script is folder-finder. It finds all the relevant maildirs for the current configuration and subscribes to them. It knows how to find both Courier-style and OfflineIMAP-style folders and normalize their names. It runs every time I run mutt, so that it will find folders that have been recently created. Unfortunately, mutt can't include the multi-line output of a script via the "source" directive or backticks mechanism, so I end up with this in my muttrc:

source `~/.mutt/folder-finder > ~/.mutt-folders; echo ~/.mutt-folders`

This minor inelegance is definitely worth the benefits.

Finally, there's make-mailcap. This program looks at WhichConfig and looks for known useful commands in $PATH, then reads in /etc/mailcap and dumps an output file into ~/.mutt/mailcap. This file is used as the mailcap file, which mutt uses to figure out how to view or print attachments. This is useful for dumping HTML mail to text (when it has no useful text alternative), or for opening pictures and PDFs in Preview, xv, or xpdf. Over time, I imagine I'll add more and more helpers to make-mailcap, but the most useful one is osx-preview-img. When mutt uses a helper program to open an attachment, it generally sees a specification like "lynx -dump -force_html '%s'" and replaces the %s with the name of a temporary file, which is deleted after the command exits.

In MacOS X, the way to open a file in a GUI application is usually to use the open command, like this:

$ open -a Preview some-image.jpg

The problem is that open exits nearly instantly, having send a request to Preview. mutt then deletes the temporary file, and Preview sends a SIGWTF. My helper program copies the tempfile to another location and has Preview open that. It never cleans up that tempfile, but since it's under /tmp, I know the OS will clean it up on reboot. In the future, I may look at using Mac::Glue to write a helper that won't leave clutter in /tmp, but I'm not too worried about it for now.

All of this stuff has been so useful to me that I feel like I should bundle it up and drop it on the CPAN, but I'm not sure whether (or how) anyone else would find much of it useful. I think I need to work more on it and see if it can be turned into a simple module to attach plugins to, sort of like Addex, but just for mutt configuration.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • From the open(1) man page:
    -W Causes open to wait until the applications it opens (or that were already open) have exited. Use with the -n flag to allow open to function as an appropriate app for the $EDITOR environment variable.
    • Errrr! How many times have I looked at the open(1) page, thinking, "How can there not be a 'stay foregrounded' option?"

      Thank you for noticing the mote in my eye!
      --
      rjbs
      • I've asked myself the very same question many times, but the -W switch must be new in 10.5. On 10.4.11, there's no mention of -W in the open(1) man page, and neither does the command itself seem to recognize the switch.

  • My idea to solve that would be much simpler: just keep a branch in git for every machine.

    Would that not work, or have unacceptable drawbacks?

    • When I start using whichconfig for things like "run with this alternate profile," I will want to have every version, or multiple versions, of config installed.
      --
      rjbs
  • Unfortunately, mutt can’t include the multi-line output of a script via the “source” directive or backticks mechanism

    Can too, if you source a pipe instead of passing a filename via backticks. From my .muttrc:

    source 'cd ~/Mail ; for f in * ; do echo "=mailboxes +$f" ; done |'

    Note the straight single-quotes instead of backticks, and the pipe at the end of the “filename.”

    Works like a charm.

    • How interesting! That seems totally undocumented. I'll give it a try.
      --
      rjbs
  • On some machines, I want HTML rendered with lynx, and if there’s no lynx, html2text will do, and so on.

    Check out vilistextum [dyndns.org] too. It renders HTML to plaintext way more nicely than lynx, and it runs instantly. (Even on my Core2Duo workstation, lynx causes a noticeable stutter when mutt opens an HTML mail; with vilistextum I don’t even notice I’m reading HTML, half the time.)

    • I've heard good things about vilistextum. I'll try it later. It isn't in MacPorts, so I'll have to ... do stuff.
      --
      rjbs