4 ms·
I use a setup very similar to this on OS X. - After using offlineimap for years, I recently switched to mbsync/isync. It is way faster and has been much more
by k2enemy 12y ago
I use a setup very similar to this on OS X.
- After using offlineimap for years, I recently switched to mbsync/isync. It is way faster and has been much more stable.
- After a stint with sup (http://supmua.org http://supmua.org), I'm now back to mutt. I really love sup's interface, but it was a little too flaky.
- I use a script called "mail" that starts a tmux session then launches mutt in it:
#!/bin/sh
tmux -2 new-session -d -s mail -n 'mutt' "export TERM=screen-256color; mutt"
tmux select-window -t 1
tmux attach-session -d -t mail
Then, in mutt I have the double-quote mapped to a macro that executes a shell command to split the tmux window and launch a read-only instance of mutt:
macro index,pager \" "<enter-command> \
unset wait_key<enter><shell-escape> \
tmux split-window -h \"mutt -R\"<enter>" "open new mutt"
This is my way of having an "async compose" pane for writing emails. I had tried replacing the mutt EDITOR variable with a command that splits the window and launches vim, but there are a lot of annoyances with that approach. Launching another mutt is way easier, and it also allows for easily viewing two emails at once.
That said, there are a lot of nice tips in here that I'll incorporate into my setup. Thanks for posting!