9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matthew Veety <mveety@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Reading gmail
Date: Sat, 19 May 2012 23:30:11 -0400	[thread overview]
Message-ID: <D3CE9742-A615-440F-BBB4-F397C0B7CB6E@gmail.com> (raw)
In-Reply-To: <dcc7cc51c82c112d77f48676a7bd160c@kw.quanstro.net>

On May 15, 2012, at 4:43 AM, erik quanstrom wrote:

> On Mon May 14 23:58:41 EDT 2012, mveety@gmail.com wrote:
>> 
>> On May 14, 2012, at 11:51 PM, John Floren wrote:
>>> 
>>> If you have a large number of messages, Erik's "nupas" is useful; IIRC
>>> it will cache messages locally so you don't have to download a ton of
>>> headers each time you start upas.
>>> 
>>> However I've found that with both old upas and nupas, there are some
>>> messages that make them choke. Sadly I can't remember what triggered
>>> it.
>>> 
>>> john
>>> 
>> 
>> My 16,000 message inbox usually make nupas and upas shit the bed. I've never had specific messages kill it though.
> 
> the nupas core should be ok with 16k messages
> 
> 	minooka; mail -f bigmbox
> 	45465 messages, 44899 unread
> 	: q
> 
> on the other hand, i can easily believe the imap mailbox type
> can't handle this.  i haven't used imap mailboxes much, and
> when i did, they were very small.  if you have specific ideas,
> and or observed problems, i'd be glad to incorporate them.
> 
> - erik
> 

It's imap. My other mail clients don't have much issue with it (alpine will choke on a slow connection), but my work machine (running 9front) is having definite issues. I'll totally look into this more for you, Erik.

PS. You have >44000 unread messages?!?!?!?!?
--
Veety


  reply	other threads:[~2012-05-20  3:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  2:51 Burton Samograd
2012-05-15  3:08 ` sl
2012-05-15  3:51   ` John Floren
2012-05-15  3:57     ` Matthew Veety
2012-05-15  8:43       ` erik quanstrom
2012-05-20  3:30         ` Matthew Veety [this message]
2012-05-20 12:45           ` erik quanstrom
2012-05-20 12:47             ` Matthew Veety
2012-05-20 13:02               ` erik quanstrom
2012-05-20 13:15                 ` Kurt H Maier
2012-05-20 13:15                 ` Bruce Ellis
2012-05-15 15:56       ` Anthony Sorace
2012-05-15 16:04         ` sl
2012-05-19 17:37     ` Akshat Kumar
2012-05-19 20:31       ` Charles Forsyth
2012-05-19 20:42       ` Anthony Sorace
2012-05-19 20:54         ` Steve Simon
2012-05-19 21:06           ` Charles Forsyth
2012-05-19 22:33             ` Kurt H Maier
2012-05-19 23:11             ` Nemo
2012-05-20 20:50             ` Ethan Grammatikidis
     [not found]     ` <CABwSpPCb0DrkDocY4Qg=8814HB1Ws=uF=jnGbcDy4j-1U7Y7Ag@mail.gmail.c>
2012-05-19 21:39       ` erik quanstrom
2012-05-15  4:08   ` 9 9
2012-05-15  5:37     ` 9 9
2012-05-15  6:41       ` Federico Benavento
2012-05-15  6:46         ` 9 9
2012-05-15  7:01         ` John Floren
2012-05-15 13:50         ` 9
2012-05-15  6:41       ` 9 9

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D3CE9742-A615-440F-BBB4-F397C0B7CB6E@gmail.com \
    --to=mveety@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).