On Mon Sep 07, 2020 at 12:49:57PM -0400, Aisha Tammy wrote: > On 9/7/20 11:52 AM, Rafael Sadowski wrote: > > On Sun Sep 06, 2020 at 04:12:04PM -0400, Aisha Tammy wrote: > >> On 9/5/20 6:08 PM, Aisha Tammy wrote: > >>> On 9/5/20 5:40 PM, Pamela Mosiejczuk wrote: > >>>> > >>>> On 2020-08-13 14:48, Aisha Tammy wrote: > >>>>>>>>> On 6/1/20 12:46 AM, Aisha Tammy wrote: > >>>>>>>>>> Hi, > >>>>>>>>>> This is quite a handy package for autoconfiguration of neomutt > >>>>>>>>>> and other utilities. I'm hoping we can get it so that a lot of the > >>>>>>>>>> newcomers who want to use neomutt won't be that daunted by the > >>>>>>>>>> dotfiles. > >>>>>>>>>> > >>>>>>>>>> I've attached the port but upstream doesn't make any tagged > >>>>>>>>>> releases, so > >>>>>>>>>> I've made it using a dated format. I'm not sure what the proper > >>>>>>>>>> method is > >>>>>>>>>> when adding versions to such packages. > >>>>>>>>>> > >>>>>>>>>> PS: upstream calls it mutt-wizard but it needs neomutt as told by > >>>>>>>>>> upstream. > >>>>>>>>>> > >>>>>>>>>> Aisha > >>>>>>>>>> > >>>>>>>>>> > >>>>> Reattaching port with updated Makefile. > >>>>> It should be building correctly now. > >>>>> > >>>>> Aisha > >>>> > >>>> I have been using this, and attach a version with a patch from Aisha for > >>>> email validation and a quick fix of mine which makes notmuch integration > >>>> work. > >>>> > >>>> I've tested config, bindings, syncing, password storage and multiple > >>>> account switching and agree this provides a very useful starting config > >>>> for users who want to get up and running. I have not tested sending PGP > >>>> encrypted mail, and the port doesn't take a user quite to the finish > >>>> line on that (and if you don't wish to encrypt your mail you'll need to > >>>> disable lines - it defaults to on), but this is an excellent resource > >>>> for a new would-be neomutt user to get set up, and also uses some > >>>> niceties like the sidebar. > >>>> > >>>> We could leave the final encryption bits as an exercise to the user > >>>> they'd need to figure out anyway, but if anyone who does habitually use > >>>> encryption can test or if anyone has thoughts about use of the default > >>>> neomutt flavor, I can't really speak to that end of things. Most of the > >>>> setup is guided, which is nice. I quite like the rest and would love to > >>>> import this. > >>>> > >>>> -pamela > >>>> > >>> > >>> OMG, So sorry, I forgot about this in my work! Thanks so much for > >>> testing!!! > >>> A nice thing is that upstream is very nice at merging our patches, > >>> They added the email validation patch into upstream code. > >>> Would you be fine with me adding your patch to upstream as well? Less > >>> work on our end. > >>> (I don't use notmuch so I was unable to test that part but everything > >>> else > >>> [multi-account and others] works) > >>> > >>> Thanks so much! > >>> Aisha > >>> > >> > >> Upstream has been receptive and added Pamela's patch as well. > >> I've added the updated port. > >> > >> OK? > >> > >> Aisha > > > > Some little tweaks: > > > > - s/GPL-3/GPLv3 > > - s/GH_COMMIT =/GH_COMMIT =/ (one space) > > > > ... and one question. Why do you use "_0" and not only YYYYMMDD. Could > > you add a syntax comment like "# commit date YYYYMMDD" over DISTNAME, > > please? > > > > Rafael > > > Hi Rafael, > I've made the tweak changes, added the comment and renamed it > to only mutt-wizard-YYYYMMDD. > > I originally kept it 0_<date> cuz if someday upstream decided to release > a tag, like 0.1, then 0_* would count as a smaller version (at least how its > done in > gentoo, which seems like an nice thing). But that's unimportant for us here. > > Thanks, > Aisha
OK rsadowski to import
