On Thu, Aug 20, 2015 at 11:29:32AM -0700, Kevin J. McCarthy wrote: > egbert. wrote: > > So we can have one config var for ‘socket timeout on idle’. This > > is to solve the hanging mutt problem which people (like me) are > > complaining about when you pack up your laptop and go somewhere > > else. And, it can be the same value for read and write. > > > Then, when you are sending or receiving mail, the timeout should be set to > > a > > second, larger value. Something like ‘socket timeout on data’. > > I'd suggest we try to get this current simple solution in first, and see > what happens. It may be that you're right and a one-config-option > solution doesn't work well, but I'd like to see what kind of feedback we > get across all mutt-users.
Ok. For myself, I can keep two muttrc’s around. Or, do :set socket_timeout = <new value> from within mutt when I want to adjust it – only I’ll have to try and figure out a way to make it rerun the init code. Grts. Allen
