Re: message stored in Sent folder even if sending fails

2016-08-02 Thread Vincent Lefevre
On 2016-07-29 12:35:31 -0500, Derek Martin wrote: > On Thu, Jul 28, 2016 at 11:12:48AM +0200, Vincent Lefevre wrote: > > I think that the right solution would be to prompt the user for > > retrying. The user should have the choice between: > > > > 1. Retry (default). > > 2. Choose a different fold

Patches for behavior change for sidebar

2016-08-02 Thread Omen Wild
First, thanks for including sidebar in the official release. I find it invaluable and allows me to use mutt in a work environment. I do have a couple quibbles with the default behavior and have attached two patches to tweak it. There are no configuration options for these patches and they soft-fai

Re: Patches for behavior change for sidebar

2016-08-02 Thread Kevin J. McCarthy
On Tue, Aug 02, 2016 at 05:17:04PM -0700, Omen Wild wrote: > First, thanks for including sidebar in the official release. I find it > invaluable and allows me to use mutt in a work environment. Hi Omen, mutt-1.6.2 does not have the sidebar in it. Our default branch in the repository has the side

mutt: 2 new changesets

2016-08-02 Thread Brendan Cully
changeset: 6748:01541185e6f4 user: Kevin McCarthy date: Tue Aug 02 19:18:46 2016 -0700 link: http://dev.mutt.org/hg/mutt/rev/01541185e6f4 Use the ctx->mx_ops instead of calling mx_get_ops() With mx_open_mailbox_append() setting the ctx->mx_ops, all contexts should have mx_ops set.

Starting towards 1.7

2016-08-02 Thread Kevin J. McCarthy
With the sidebar, buffy fixes, trash folder, and browser updates merged, I'd like to start thinking about a 1.7 release. There has been a good conversation about the order of sending vs fcc, and I think the ideas proposed have merit, but I want to take some time to play with that idea. This would

Re: Patches for behavior change for sidebar

2016-08-02 Thread Omen Wild
Quoting Kevin J. McCarthy on Tue, Aug 02 18:48: > > The second patch doesn't match against the latest version, and I believe > it may be that neomutt-1.6.2 didn't include the fixes in > https://dev.mutt.org/hg/mutt/rev/6f2fe8f32dab and >https://dev.mutt.org/hg/mutt/rev/ec4c113a3d2b >f