Closed dan-mi-sun closed 7 years ago
ACK yes neomutt should be contemplated, not sure it will loose features (in particular hcache), however this can be solved with a simple check just like it is done in the function is_mutt_kz
for detecting mutt-kz flavor.
Recompile neomutt with --enable-hcache
:)
Here's my configuraion options: @jaromil can you share yours so we can see what's the minimum to work without issues?
$ mutt -v | grep 'Configure options'
Configure options: '--prefix=/usr' '--build=x86_64-gentoo-linux-musl' '--host=x86_64-gentoo-linux-musl' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--disable-dependency-tracking' '--disable-silent-rules' '--docdir=/usr/share/doc/mutt-1.7.1' '--htmldir=/usr/share/doc/mutt-1.7.1/html' '--libdir=/usr/lib' '--enable-pgp' '--disable-debug' '--enable-gpgme' '--enable-imap' '--disable-nls' '--disable-nntp' '--enable-pop' '--enable-sidebar' '--enable-smime' '--enable-smtp' '--enable-notmuch' '--without-idn' '--without-gss' '--with-curses=/usr' '--enable-compressed' '--enable-external-dotlock' '--enable-nfs-fix' '--sysconfdir=/etc/mutt' '--with-docdir=/usr/share/doc/mutt-1.7.1' '--with-regex' '--with-exec-shell=/bin/sh' '--enable-hcache' '--without-tokyocabinet' '--without-qdbm' '--with-gdbm' '--without-bdb' '--with-ssl' '--with-sasl' '--with-homespool=Maildir' 'build_alias=x86_64-gentoo-linux-musl' 'host_alias=x86_64-gentoo-linux-musl' 'CFLAGS=-march=westmere -O2 -pipe' 'LDFLAGS=-Wl,-O1 -Wl,--as-needed'
$ mutt -v | grep 'Configure options'
Configure options: '-enable-notmuch' '-enable-sidebar' '-enable-gpgme' '--disable-nls'
Is the one which has caused the issues I have noted above ^
@parazyd your suggestion of -enable-hcache
fixed it.
$ mutt -v | grep 'Configure options'
Configure options: '-enable-notmuch' '-enable-sidebar' '-enable-gpgme' '--disable-nls' '--with-ssl' '-enable-hcache' '--with-regex' '-enable-imap' '-enable-pgp'
I also added a few others which you have highlighted :)
Thanks again for your help!
Have upgraded to neomutt from mutt and am getting the following output prior to opening
jaro
It is not breaking jaromail, just adding an annoying keystroke to the workflow.
I am getting the following even after running
jaro update
Here are the lines from /home/dan/Mail/.mutt/rc
And there does exist /home/dan/Mail/.mutt/cache
And corresponding lines from /usr/local/share/jaromail/.mutt/general
Although the above does not experientially seem to be effecting jaromail - would be sweet not to have additional keystroke when entering mail each time ;)
Thanks in advance for input!
8^D