-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, October 5 at 07:58 AM, quoth Joseph:
>So it seems the problem was caused by the statement header_cache
>below
>
>I had in muttrc:
>set header_cache="~/.mutt_headercache/"
>
>Is the header cache build into mutt or do I need to activate it with the
>statement above?
Yes the header cache is built into mutt, and yes you need to activate
it with that configuration setting.
If it helps, mutt stores its internal structures in that headercache
(so it doesn't have to do any parsing, which would be slow). When you
change options, like adding pop3 support, you change the contents of
mutt's internal structures. Unfortunately, as of yet, mutt doesn't do
much in the way of verifying that the header cache is correct. This
makes it faster, but at the expense that reconfiguring can sometimes
cause trouble.
~Kyle
- --
You never truly understand a thing until you can explain it to your
grandmother.
-- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFHBk/XBkIOoMqOI14RArXrAKDLUt+7+YxAUy7DZXy8uFkhAylXCQCg4I3Y
PwowU03DXw0SsLxjdFDENpY=
=a6Qc
-----END PGP SIGNATURE-----
