Re: [Mutt] #3207: Conform to XDG Base Directory Specification

2013-10-25 Thread Mutt
#3207: Conform to XDG Base Directory Specification --+-- Reporter: wraichia | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt |Version: Resolution:

Re: [Mutt] #3207: Conform to XDG Base Directory Specification

2013-10-25 Thread Michael Elkins
On Fri, Oct 25, 2013 at 04:03:10PM -, Mutt wrote: #3207: Conform to XDG Base Directory Specification --+-- Reporter: wraichia | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component:

Re: [Mutt] #3207: Conform to XDG Base Directory Specification

2013-10-25 Thread Mutt
#3207: Conform to XDG Base Directory Specification --+-- Reporter: wraichia | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt |Version: Resolution:

Re: [Mutt] #3207: Conform to XDG Base Directory Specification

2013-10-25 Thread Mutt
#3207: Conform to XDG Base Directory Specification --+-- Reporter: wraichia | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt |Version: Resolution:

Re: [PATCH 6 of 6] Add the crypt_opportunistic_encrypt option and calls

2013-10-25 Thread Michael Elkins
On Fri, Mar 15, 2013 at 09:03:53PM -0700, Kevin J. McCarthy wrote: This patch creates the OPTCRYPTOPPORTUNISTICENCRYPT option and documentation. It also adds calls to crypt_opportunistic_encrypt() during initial message composition, after updating to, cc, or bcc, and after editing the message (i

Re: [PATCH 6 of 6] Add the crypt_opportunistic_encrypt option and calls

2013-10-25 Thread Kevin J. McCarthy
Michael Elkins wrote: > I see a potential problem here: If the user has manually requested > encryption or disabled it for the current message, but has > opportunistic encryption enabled, it may override what the user has > set manually. That's a good point. Right now I can think of three imperf