search

fastsupply / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

Ability to enable/disable notifications by whether they match a regular expression #32

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What feature or enhancement do you propose?
A setting in the Notification section of the Applications tab containing list 
of regular expressions to 
be attempted in order, along with an enabled state. When the application posts 
this notification, 
Growl would go down the list of regular expressions; whenever an expression 
matches the title or 
description (this could be set per expression), Growl would set the enabled 
state of the notification 
being examined to whatever value corresponds to the expression.

What problem does it solve/What benefit does it provide?
It would enable users to set up conditional enablement of notifications based 
on their content, not 
just on the categories that the application assigned to them.

Original issue reported on code.google.com by prhgr...@gmail.com on 6 Oct 2009 at 10:55

GoogleCodeExporter commented 9 years ago 
One downside is that this could be a slippery slope of users wanting ever more 
customization options (e.g., flow 
control, variables, Boolean operators).

Discussion of a good way to implement regular-expression-based filtering, 
including better ways than the one I 
suggested above, is welcome.

Original comment by prhgr...@gmail.com on 6 Oct 2009 at 10:57

GoogleCodeExporter commented 9 years ago 
I don't think we should have regular expression filters. I do think we should 
have intelligent filtering/spam 
filtering of some kind. I use and like regex (pcre!) but this seems way 
overboard for what Growl does.

Original comment by chrisf.g...@gmail.com on 6 Dec 2009 at 5:05

GoogleCodeExporter commented 9 years ago 
A related request that came in today 
(http://groups.google.com/group/growldiscuss/t/fe67b0d7d9502f0b) is 
to be able to set notifications' stickiness by the same means.

Original comment by prhgr...@gmail.com on 13 Jan 2010 at 3:35

GoogleCodeExporter commented 9 years ago 
We should probably talk this one our Peter. Around the 1.4 range for 2.0.

Original comment by chrisf.g...@gmail.com on 2 May 2010 at 11:19

GoogleCodeExporter commented 9 years ago 
Moving to 2.0.

Original comment by chrisf.g...@gmail.com on 29 Jul 2010 at 4:41

GoogleCodeExporter commented 9 years ago

Original comment by chrisf.g...@gmail.com on 30 Jul 2010 at 2:28

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 11 Nov 2011 at 1:21

GoogleCodeExporter commented 9 years ago 
Growl 2.1 has gained rules via applescript, see #535 for more information.  
While our rules implementation may yet need tweaking and work (as listed on 
that ticket), this is certainly doable now.  Flagging as fixed in source.

Also, yes, I know, Applescript doesn't have reg ex baked in, but there are 
plenty of ways for the determined user to do it, and we will want to add that 
to the documentation potentially.

Original comment by dan...@growl.info on 31 Oct 2012 at 9:55