On Mar 27, Simon White [[EMAIL PROTECTED]] wrote: > 27-Mar-02 at 08:33, Jeremy Blosser ([EMAIL PROTECTED]) wrote : > > On Mar 27, Simon White [[EMAIL PROTECTED]] wrote: > > > Secondly, on a dialup link, it's too slow if you SSH somewhere and you > > > have to /compose/ mail. For moving around the screen, even if you're good > > > with vim (or whatever you set $THE_ONE_TRUE_EDITOR to) is not responsive > > > enough. And if you have a connection that is fast enough not to notice > > > that, you can probably download mail fast anyway. I SSH to my workstation > > > from a fixed IP authenticated dialup connection at home and it's too slow > > > to compose mail, although reading mail is quicker with Mutt than PINE > > > running locally and just fetching mail from the server. This is largely > > > due to the pager allowing faster browsing of mail. > > > > Weird. I used to do this all the time before I had DSL, and it was never a > > problem. And the mail server I was connecting to was a 486 w/12M of RAM. > > The initial connection was slow, but after that it was fine. > > > > Are you using SSH compression? It helps a lot. > > How fast do you type? I'm at ~55wpm if typing easy mail where I don't > think too much.
Faster than that. > Not sure if I had compression set. In any case, I don't like ANY delay > between keypress and letter appearing on screen, since I'm not looking at > the keys as I type, and if the display is constantly "catching up" it > throws me right off. You probably didn't have compression set. Try running ssh with the -C option. It makes a dramatic difference.
msg26283/pgp00000.pgp
Description: PGP signature
