Re: terminals and mutt

[Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday, August 14 at 09:03 PM, quoth mimosinnet@xxxxxxxxx:
>> I like the fact that I can put mutt in the background (^Z) to 
>> quickly check something and then come back (fg) without moving to 
>> another terminal. Plus, for me, mutt dies whenever my internet 
>> connection dies (some weird interaction with the ssl library, I 
>> think), and getting a new terminal every time would be annoying.
>
> I have just tried this and read the "job control" section of the bash 
> manual. I can use these simple commands to have multiple instances of 
> mutt with different accounts. No need for tabbed terminals....

Well... not exactly. The downside of using job control for multiple 
(remote) accounts is that, when mutt has been stopped, it cannot keep 
the network connection alive (it can't do *anything*: it's stopped, 
and is therefore ineligible for CPU-time). Being paused for a minute 
or two is one thing; the server probably won't notice. Being paused 
for five or more minutes, though, and you're increasingly likely to be 
dropped by the server. If reconnecting is fast, then you may not care, 
but it's something to remember.

> Thanks very much for the advice, it has saved me lots of time 
> exploring a dead-end. Looking at the command you have mentioned, I 
> have found that stty -a gives me the key bindings I should avoid in 
> mutt. I very much appreciate these tips.

Happy to help!

~Kyle
- -- 
The price of freedom of religion, or of speech, or of the press, is 
that we must put up with a good deal of rubbish.
                                                      -- Robert Jackson
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iEYEARECAAYFAkikmjQACgkQBkIOoMqOI15WUACdH/v+Cs/BwfcmWT39g0LqUOWO
ehYAn0v0ks+FLu4Gzm74azEoxOJGXDaY
=xhK/
-----END PGP SIGNATURE-----