On Tue, Apr 11, 2017 at 09:58:59AM -0700, Kevin J. McCarthy wrote: > On Mon, Apr 10, 2017 at 12:41:54PM -0700, Will Yardley wrote: > > On Mon, Apr 10, 2017 at 01:43:46PM -0400, Derek Schrock wrote: > > > If you were to take it a couple extra steps further could you have > > > $beep_new for currently open box, $beep_new_buffy be a list of mailboxes > > > from mailboxes such that you want notifications/beeps from? > > > > > > set beep_new_buffy = * # All mailboxes in mailboxes > > > beep > > > set beep_new_buffy = boxA, boxB, boxZ # Beep when A, B, Z are updated. > > > > I think zsh and bash, at least, can do this natively, maybe this is > > functionality that a lot of people would just accomplish in their shell > > of choice? > > Just to be clear, this patch is not adding new beep functionality to > mutt. A single option ($beep_new) currently controls beeping for two > cases: new mail in the current mailbox, and new mail polled by buffy. > The patch splits out an option so that they can be individually turned > off/on.
Yeah, I get that, I just kind of agree with your initial comment about micro-options (and was also pointing out that it's possible to do the buffy notifications in one's shell). w
