Luis Mochan wrote on 07/26/12 at 21:24:49 -0500: > I receive my email at a desktop in my office and I access it through > mutt at my office and remotely through my laptop using IMAP. Thus, I > have configuration files at my desktop and at my laptop. However, > there are parts of the configuration which should be identical, such > as my list of alias and a few macros. Having several copies yields > occasional inconsistencies. Is there a reasonable way to keep some > configuration files at my office and source them remotely from my > laptop when I start mutt? Similarly, I would like to be able to update > the files at my office when I define a new alias at my laptop. An > alternative would be to use a revision control system to update and > synchronize the relevant files among my computers, but I wonder if > there is a simpler solution.
What about, instead of having your laptop connect to the desktop over IMAP, you just ssh into the desktop from the laptop, and run the copy of mutt that lives on your desktop to read the mail that lives on your desktop? That way, there is only one copy of all your config files, and one copy of mutt. If you define a new alias from *within* mutt (or within an editor called from your ssh session), it is already in the one place it belongs: the desktop in your office. I do this sometimes with one of my accounts. One of its advantages is that using the remote mutt is really snappy, because it doesn't have to mess with headers and caching. Even if it did mess with that, it wouldn't have to be downloaded first. One of the disadvantages is that one can't just hit 'v' then 'Return' to view non-plain-text attachments like PDFs (unless you feel like messing with X-forwarding and such). But when that happens I just use scp to pull the attachment to my local machine. --Jack
