On Wed, May 22, 2019 at 11:42:39PM -0700, Will Yardley wrote:
On Thu, May 23, 2019 at 08:24:11AM +0200, Alexander Dahl wrote:On Thu, May 23, 2019 at 01:47:15PM +1000, m...@raf.org wrote:> This might not be the right place to report this but Is the mutt mailing list the right place to discuss neomutt problems? (Serious question, I don't actually know.)Short answer (not an official one, but just based on the discussion I've seen), no.
In general, as Will says, no. But segfaults are always of interest, in case the bug is present in Mutt too. Particularly for easy to reproduce, clearly common functionality.
In this case, the bug was fixed in commit 786aa6cf for release 1.8.1.I like to encourage people to post to mutt-users first, as was done here, and if it's clear there is a bug in Mutt, create a ticket on gitlab: <https://gitlab.com/muttmua/mutt/issues>.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
