On 2019/11/06 09:55, [email protected] wrote: > Synopsis: neomutt segmentation faults when command line email sent
neomutt recently had an update with over a year's refactoring work and as mentioned in the commit log : : update to neomutt-20191025, as upstream say this has a lot of changes : but should be ok for general use. : : see https://github.com/neomutt/neomutt/releases/tag/2019-10-25 for more : information and help request. This particular bug was fixed upstream a couple of days ago, https://github.com/neomutt/neomutt/issues/1943 I'll backport that commit now, but I would expect another upstream release including it fairly soon anyway. > (I don't think this will be on the ports list, but I apologize > if that happens. I accidentally sent to ports before subscribing.) Generally unless a problem seems specific to OpenBSD it's best to report bugs upstream. Maybe cc or send the ticket URL to the port maintainer ("pkg_info neomutt" will show you this) or to ports@. This ports-bugs@ list is pretty much unused and you're lucky I saw it here!.
