Don't forget to launch any secondary instances of mutt with -R, or you'll encounter conflicts.
I've been searching for the right way to launch the editor in a new tmux pane, although apparently getting that to work smoothly would take a patching effort.
Default / typical behavior is for mutt to update the mailbox message state (new, unread, read, replied) when closing the mailbox. Using the -R flag prevents this behavior.
Forgetting to do so is more an annoyance than an End of the World Event, but it's an annoyance which can be avoided with a really simple flag use.
It's something I read when I was getting started with mutt.
Perhaps is much less of a deal than I thought, after giving a cursory Google I can't seem to find what I read that gave me that impression and I don't see any major warnings not to.
Hm, I might follow that idea (open in a new terminal window or split screen). I'd somehow have to get the original message as a quote for the new message.
You can always open the mailbox first and grab the message you want to reply to:
mutt -Rf <mailbox name>
... will open the given mailbox in read-only mode (so as not to update read flags and such).
In practice, I generally run mutt within screen, with multiple frequently-accessed mailboxes open. I switch mailboxes by moving between screen buffers.
Comments
I love mutt! Unfortunately, I often write emails while looking at another one, which I couldn't make work with mutt. Any ideas?
You could use a terminal multiplexer (tmux, screen, etc) to just split-screen your terminal.
Don't forget to launch any secondary instances of mutt with -R, or you'll encounter conflicts.
I've been searching for the right way to launch the editor in a new tmux pane, although apparently getting that to work smoothly would take a patching effort.
I launch innumerable copies of mutt without -R, and have never had any conflicts.
Like the original poster, I'm using offlineimap and maildir's entirely.
What kind of conflicts do you get?
Default / typical behavior is for mutt to update the mailbox message state (new, unread, read, replied) when closing the mailbox. Using the -R flag prevents this behavior.
Forgetting to do so is more an annoyance than an End of the World Event, but it's an annoyance which can be avoided with a really simple flag use.
It's something I read when I was getting started with mutt.
Perhaps is much less of a deal than I thought, after giving a cursory Google I can't seem to find what I read that gave me that impression and I don't see any major warnings not to.
You can launch a compose session from any terminal. "mutt -s 'subject line'" will prompt for recipient(s) and drop you into an editor for composing.
You can even pipe output straight to mutt:
Hm, I might follow that idea (open in a new terminal window or split screen). I'd somehow have to get the original message as a quote for the new message.
You can always open the mailbox first and grab the message you want to reply to:
... will open the given mailbox in read-only mode (so as not to update read flags and such).In practice, I generally run mutt within screen, with multiple frequently-accessed mailboxes open. I switch mailboxes by moving between screen buffers.