Re: too many messages saturates slow link

2001-04-01 Thread Carlos Puchol

great! problem solved. thanks!

David Champion [EMAIL PROTECTED] writes:
 Subject: Re: too many messages saturates slow link
 
 On 2001.03.30, in [EMAIL PROTECTED],
   "Suresh Ramasubramanian" [EMAIL PROTECTED] wrote:
  Carlos Puchol proclaimed on mutt-users that: 
  
   Reading /var/spool/mail/me... 1869 (33%)
   
   this saturates my modem line for a little while.
  
   is there some way to turn it
   off or just make it show the XX% part (assuming
   it is not printed at every message)?
   
   That's because mutt has to read the contents of your mbox format mailbox.
   Switch to (say) maildir.  Much faster (and better, if you handle large amounts
   of mail).
 I get a lot of mail, and don't need to use maildir for performance
 reasons.  Mbox works fine.  Changing to maildir won't solve this
 problem, either, unless for some odd reason maildir switches out the
 progress report.
 What you probably want is to set the read_inc variable, or to make it
 larger than it is already.  $read_inc indicates how often to update the
 status report line whlie reading a mailbox.  For example, setting it
 to 50 makes the status line update every 50 messages, instead of with
 each message.
 - -- 
  -D.  [EMAIL PROTECTED]NSITUniversity of Chicago




too many messages saturates slow link

2001-03-30 Thread Carlos Puchol


hi, when i connect via a slow link to my box, i get this
when i type mutt:

Reading /var/spool/mail/me... 1869 (33%)

this saturates my modem line for a little while.
because (it seems) there is a lot of redraws printing
the message count (one line per message?).

is there some way to turn it
off or just make it show the XX% part (assuming
it is not printed at every message)?

thanks,

-c




Re: too many messages saturates slow link

2001-03-30 Thread Suresh Ramasubramanian

Carlos Puchol proclaimed on mutt-users that: 

 Reading /var/spool/mail/me... 1869 (33%)
 
 this saturates my modem line for a little while.

 is there some way to turn it
 off or just make it show the XX% part (assuming
 it is not printed at every message)?
 
 That's because mutt has to read the contents of your mbox format mailbox.
 Switch to (say) maildir.  Much faster (and better, if you handle large amounts
 of mail).
 
 You'd have to suggest this to your provider, if you dont run your own server.
 
-s (or pop the mails down with fetchmail and run maildir locally)

-- 
Suresh Ramasubramanian + Wallopus Malletus Indigenensis
mallet @ cluestick.org + Lumber Cartel of India, tinlcI
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin



Re: too many messages saturates slow link

2001-03-30 Thread David Champion

On 2001.03.30, in [EMAIL PROTECTED],
"Suresh Ramasubramanian" [EMAIL PROTECTED] wrote:
 Carlos Puchol proclaimed on mutt-users that: 
 
  Reading /var/spool/mail/me... 1869 (33%)
  
  this saturates my modem line for a little while.
 
  is there some way to turn it
  off or just make it show the XX% part (assuming
  it is not printed at every message)?
  
  That's because mutt has to read the contents of your mbox format mailbox.
  Switch to (say) maildir.  Much faster (and better, if you handle large amounts
  of mail).

I get a lot of mail, and don't need to use maildir for performance
reasons.  Mbox works fine.  Changing to maildir won't solve this
problem, either, unless for some odd reason maildir switches out the
progress report.

What you probably want is to set the read_inc variable, or to make it
larger than it is already.  $read_inc indicates how often to update the
status report line whlie reading a mailbox.  For example, setting it
to 50 makes the status line update every 50 messages, instead of with
each message.

-- 
 -D.[EMAIL PROTECTED]NSITUniversity of Chicago




Re: too many messages saturates slow link

2001-03-30 Thread Wade A. Mosely

Carlos Puchol wrote:
 this saturates my modem line for a little while.
 because (it seems) there is a lot of redraws printing
 the message count (one line per message?).
 
 is there some way to turn it
 off or just make it show the XX% part (assuming
 it is not printed at every message)?

Have you tried setting $read_inc and $write_inc to greater
values?  Perhaps that would help.

-- 
Linux: The Choice of the GNU Generation