neomutt: where is hcache?

[kampfflunder]

Hi,

how do I enable header cache (+hcache)?

It was available in NeoMutt 20180512 (which I restored from backup) In recent NeoMutt 20180716 it is not available anymore.

Header cache is extremely useful for larger mailboxes, can you please give it back?

~$ mutt -v
NeoMutt 20180716
[…]
Einstellungen bei der Kompilierung:
  +bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens +getaddrinfo
  -gnutls -gpgme -gss -hcache -homespool +idn -locales_hack -lua +meta
  -mixmaster +nls -notmuch +openssl +pgp -sasl +smime +start_color
  +sun_attachment +typeahead

[mf2k (Frank Schima)]

In the future, please add the port maintainer(s) to Cc (port info --maintainers neomutt), if any.

[lbschenkel (Leonardo Brondani Schenkel)]

If you enable one of the database variants:

   db4: Support Berkeley DB database
   db5: Support Berkeley DB database
   gdbm: Support GNU dbm database
   kyotocabinet: Support Kyoto Cabinet database
   lmdb: Support LMDB database
   qdbm: Support QDBM database
   tokyocabinet: Support Tokyo Cabinet database

Then the port should build with header cache enabled. Please let me know if that is not the case for you.

[kampfflunder]

Replying to lbschenkel:

If you enable one of the database variants:

   db4: Support Berkeley DB database
   db5: Support Berkeley DB database
   gdbm: Support GNU dbm database
   kyotocabinet: Support Kyoto Cabinet database
   lmdb: Support LMDB database
   qdbm: Support QDBM database
   tokyocabinet: Support Tokyo Cabinet database

Then the port should build with header cache enabled. Please let me know if that is not the case for you.

Well, that worked. It was not clear to me that enabling a storage backend would give me hcache.

Ticket can be closed.

Thank you again!

[lbschenkel (Leonardo Brondani Schenkel)]

In 1bbddc5287cd387173d61e772148724ba4a9ebcd/macports-ports (master):

neomutt: clarify variant descriptions

See: #57972

[lbschenkel (Leonardo Brondani Schenkel)]

I agree that it is not very straightforward. This reflects NeoMutt build options (there's no hcache there either and it is controlled by enabling a storage back-end). I reworded the variant descriptions to make that clearer:

   db4: Enable header cache using Berkeley DB database
   db5: Enable header cache using Berkeley DB database
   gdbm: Enable header cache using GNU dbm database
   kyotocabinet: Enable header cache using Kyoto Cabinet database
   lmdb: Enable header cache using LMDB database
   qdbm: Enable header cache using QDBM database
   tokyocabinet: Enable header cache using Tokyo Cabinet database