Re: NeoMutt 20170113 (1.7.2) (debian9) segfaults on readonly mbox

2019-05-23 Thread Kevin J. McCarthy
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

Re: NeoMutt 20170113 (1.7.2) (debian9) segfaults on readonly mbox

2019-05-23 Thread Will Yardley
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

Re: NeoMutt 20170113 (1.7.2) (debian9) segfaults on readonly mbox

2019-05-23 Thread Alexander Dahl
Hello raf, 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 > I've just discovered that the mutt package on debian9 > stable (or rather NeoMutt 20170113 (1.7.2)) segfaults > if you ask it to write to a readonly mbox file. It >

NeoMutt 20170113 (1.7.2) (debian9) segfaults on readonly mbox

2019-05-22 Thread mutt
Hi, This might not be the right place to report this but I've just discovered that the mutt package on debian9 stable (or rather NeoMutt 20170113 (1.7.2)) segfaults if you ask it to write to a readonly mbox file. It happened several times yesterday before I realised what was wrong (and yes, I did