| Newsgroups |
gmane.mail.ifile.general |
| Message-ID |
<[email protected]> |
Jason Rennie <[email protected]> writes:
> > is nearly 840 meg.
>
> 840k I hope?
Er, yeah, I'm a dunce. 840K.
> This has been discussed in the past, but hasn't been implemented. It
> would be some work and would add complexity to ifile. Certainly worth
> pursuing if we determine that it is necessary, but there's at least one
> thing to try that's much easier that might satisfy you.
If I were to take a crack at this, would that be productive, or do you
prefer to do the core coding yourself?
> If you are currently using the --query-insert option (-Q) to filter new
> messages, try using the --query option (-q) and build .idata (e.g. run
> knowledge_base.mh via cron) once a day to pick up new messages. This will
> also speed up refiles---there's no need to hook them into ifile since
> they'll be picked up with the daily .idata build.
I'd have to adapt knowledge_base.mh for the gnus environment, but
that's not the real problem; the real problem is simply that in the
last 48 hours, I've gotten totally addicted to being able to put the
first message of a thread into its own class, and have the rest of the
messages which show up over the day turn up in that class. I can't go
back now ;-)
That said, even
ifile -q -c
takes about .4 seconds on my 600Mhz Alpha; that adds up fast...
(What amplifies the problem is that what I think is the "right way" to
hook ifile into gnus has me invoking ifile twice for every message ---
once with -q to get a recommendation, and later with -i to assert the
final decision.)
Jeremy