Re: mutt 1.12.0 release schedule
Kevin J. McCarthy:
I've added some notes on the 1.12 release to the UPDATING file in git.
For convenience, I take the liberty to crosspost it here in full:
1.12.0 (unreleased)
! $ssl_use_tlsv1 and ssl_use_tlsv1_1 now default to unset.
+ $auto_subscribe, when set, automatically adds an email with the List-Post
header to the subscribe list.
! Fcc now occurs after sending a message. If the fcc fails, mutt will prompt
to try again, or to try another mailbox.
+ Basic protected header ("memory hole") support added for the Subject header.
See the config vars: $crypt_protected_headers_read,
$crypt_protected_headers_save, $crypt_protected_headers_subject,
and $crypt_protected_headers_write.
! Color names can be prefixed with "light" in addition to "bright". "bright"
colors are bold face, while "light" are non-bold.
! Color commands can now include an attribute (e.g. bold, underline).
! $pgp_use_gpg_agent defaults set.
+ in the browser menu allows entering nested maildir
directories.
+ replies to all, but preserves To recipients in the reply.
+ $include_encrypted, default unset, prevents separately encrypted contents
from being included in a reply. This helps prevent a decryption oracle
attack.
! With gpgme >= 1.11, recipient keys with a trailing '!' now force subkey use,
as with classic gpg.
! In send mode, %{charset} mailcap expansion uses the current charset of the
file.
+ $imap_fetch_chunk_size allows fetching new headers in groups of this size.
This might help with timeouts during opening of huge mailboxes.
If you have huge mailboxes, you should also try $imap_qresync.
! can be invoked from the pager too.
+ The $forward_attachments quadoption allows including attachments in
inline-forwards (i.e. $mime_forward unset, $forward_decode set.)
https://gitlab.com/muttmua/mutt/blob/master/UPDATING
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
signature.asc
Description: PGP signature
Re: mutt 1.12.0 release schedule
On Sun, Apr 28, 2019 at 12:07:57PM -0700, Kevin J. McCarthy wrote: For those able and willing, now would be a good time to check out and build from master. I'll try to add notes to the UPDATING file in the next few days, so you know what to test, but overall "day-to-day use" testing would be quite helpful too. I've added some notes on the 1.12 release to the UPDATING file in git. I'm sure I need to go through it a few more times to fix things and make things clearer. Please feel free to suggest improvements or ask questions if something is unclear. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: mutt 1.12.0 release schedule
* Kevin J. McCarthy [04-28-19 15:08]: > Hi Everyone, > > It's about time to start finalizing for the 1.12 release. There are a few > more things I'd like to try to get in, so I'm setting the freeze date for > Friday May 10th. On that day, I'll email the translation team and give them > a couple weeks to work on translations. If all goes according to plan, I'll > release during the weekend of May 25-26. > > For those able and willing, now would be a good time to check out and build > from master. I'll try to add notes to the UPDATING file in the next few > days, so you know what to test, but overall "day-to-day use" testing would > be quite helpful too. > > For distribution maintainers, please note there were code formatting as well > as internal changes this cycle, which may make external patches more > difficult to apply. I cleaned up indentation, reformatted the code, and > have also continued replacing fixed size strings with dynamic buffers. > External patches relying on some of the changed data structures may not > compile or function properly. I would suggest taking a look at how your > patches to git master apply as soon as you can. tks, your efforts are appreciated. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
