Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Will Yardley
On Tue, Mar 08, 2016 at 10:34:07AM +0100, Moritz Barsnick wrote: > On Mon, Mar 07, 2016 at 19:34:55 -0600, Derek Martin wrote: > > Though, if you really need them, the C standard has provided these > > two since 2008, and GLIBC, and I'd imagine BSD libc, for probably > > considerably longer (though

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Derek Martin
On Tue, Mar 08, 2016 at 01:20:51PM -0500, Ben Boeckel wrote: > > Yeah, looked into this for a minute, and determined it's atrocious. > > Should lead to mail store corruption unless you're only using maildir. > > The fact that Mutt isn't multithreaded is not interesting; the fact > > that multiple p

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Ian Collier
On Tue, Mar 08, 2016 at 11:53:03AM -0600, Derek Martin wrote: > Yeah, looked into this for a minute, and determined it's atrocious. > Should lead to mail store corruption unless you're only using maildir. > The fact that Mutt isn't multithreaded is not interesting; the fact > that multiple processe

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Ben Boeckel
On Tue, Mar 08, 2016 at 11:53:03 -0600, Derek Martin wrote: > On Tue, Mar 08, 2016 at 04:39:57PM +, Richard Russon wrote: > > > How do you ensure data integrity of, say, an mbox mailstore if you're > > > not locking? > > > > Don't know. > > > > https://github.com/neomutt/neomutt/commit/5adde0

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Derek Martin
On Tue, Mar 08, 2016 at 04:39:57PM +, Richard Russon wrote: > > How do you ensure data integrity of, say, an mbox mailstore if you're > > not locking? > > Don't know. > > https://github.com/neomutt/neomutt/commit/5adde051f0ae67bfc8aeea0a26060c4e6b0685e4 Yeah, looked into this for a minute, a

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Richard Russon
On Mon, Mar 07, 2016 at 07:34:55PM -0600, Derek Martin wrote: > On Mon, Mar 07, 2016 at 04:30:29PM +, Richard Russon wrote: > > Some are from Karel Zak's Notmuch repository; the others are mine. The four patches you're concerned about are from mutt-kz. I split them out of that repo in order to

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Moritz Barsnick
On Mon, Mar 07, 2016 at 19:34:55 -0600, Derek Martin wrote: > be avoided. Though, if you really need them, the C standard has > provided these two since 2008, and GLIBC, and I'd imagine BSD libc, > for probably considerably longer (though I'm too lazy to actually > look). If your system is runnin

Re: NeoMutt[2/4] - Bug Fixes

2016-03-08 Thread Matthias Andree
Am 08.03.2016 um 02:34 schrieb Derek Martin: > On Mon, Mar 07, 2016 at 04:30:29PM +, Richard Russon wrote: >> This "feature" is small collection of bug fixes. >> Some are from Karel Zak's Notmuch repository; the others are mine. > > Are the changes implemented in the patches documented anywher

Re: NeoMutt[2/4] - Bug Fixes

2016-03-07 Thread Derek Martin
On Mon, Mar 07, 2016 at 04:30:29PM +, Richard Russon wrote: > This "feature" is small collection of bug fixes. > Some are from Karel Zak's Notmuch repository; the others are mine. Are the changes implemented in the patches documented anywhere? I'm interested to know more about some of these,

NeoMutt[2/4] - Bug Fixes

2016-03-07 Thread Richard Russon
This "feature" is small collection of bug fixes. Some are from Karel Zak's Notmuch repository; the others are mine. * mute build warning * build fix for po package name * fix %* index_format * Add browser sort by description, message count and new message count * Use unlocked libc IO everywhe