-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Saturday, June 20 at 04:02 PM, quoth Rocco Rutte:
>Hi,
>
>* Rocco Rutte wrote:
>
>> I think I'll go with the warning for now.
>
>Note to self: I should at least test it. Mutt doesn't allow linking a
>message without an ID ever since the editing th
On Sat, 20 Jun 2009 21:28:41 +0800, Rocco Rutte wrote:
Hi,
* Wu, Yue wrote:
But it's annoying all the groups show up in the view all the time, I
just want
to see the groups that have mails, others should be hiden or deleted.
Why don't you remove them then?
Rocco
Why need I to be borin
Hi,
* Rocco Rutte wrote:
> I think I'll go with the warning for now.
Note to self: I should at least test it. Mutt doesn't allow linking a
message without an ID ever since the editing threads patch was applied.
Rocco
Hi,
* Marianne wrote:
> I'd certainly pefer sync-mailbox to clearing the header cache for
> large maildirs.
As I wrote, this won't help. The problem is with older mutts, that when
you sync-mailbox, the changes you make do _not_ make it into header
cache. Thus, when you open the folder the next t
Hi,
* Kyle Wheeler wrote:
> That's what I figured. I suppose another way of putting it is: since
> it's entirely possible to receive a message that does not have a
> Message-ID header (e.g. an email server that obeys RFCs 821 and 2821
> but not 5821... particularly since only 821 has received the
Hi,
* Wu, Yue wrote:
> But it's annoying all the groups show up in the view all the time, I just want
> to see the groups that have mails, others should be hiden or deleted.
Why don't you remove them then?
Rocco
Alexandre 20-Jun-09 09:03:
> Le vendredi 19 juin de l'année 2009, vers 14 heures et 45 minutes, Rocco
> Rutte écrivait:
> > So you need to remove the header cache for that folder after
> > you edited threads.
>
> Yes! It does work.
You could alternatively try to do an explicit sync-mailbox ("$"
Le vendredi 19 juin de l'année 2009, vers 14 heures et 45 minutes, Rocco Rutte
écrivait:
> * Alexandre wrote:
> > I do not know if Header caching is enabled on this version.
>
> You can check that by issueing ':set ?header_cache' within mutt. The
> problem is (for the latest version: was) that mu
