andrewjfreyer
-
Posts
2 -
Joined
-
Last visited
Content Type
Blogs
Gallery
Downloads
Events
Profiles
Forums
Articles
Media Demo
Posts posted by andrewjfreyer
-
-
I think it'd be great to have the ability to perform actions either as a workflow trigger or a snippet replace trigger that match against a pattern (e.g., regex) in lieu of a static string.
For example, a pattern such as:
\b(etc\.|et seq\.|arguendo)\b
... that matches various latin phrases or abbreviations between word boundaries could trigger an action to italicize (⌘+i) the matched group in whatever app receives the text input. Of course, these can be manually added via traditional workflows, but this would be more elegant.
As another example:
@([a-zA-Z ]{2,})
might be used as a (rudimentary) trigger to search through a contact list and replace the @MATCH with an actual email address, a first name, last name, whatever. For example, I could envision a system where @john doe replaces the matched group with an email address for a matching contact card, whereas #john doe replaced the match with the phone number, whereas @ig:john doe replaces with an instagram handle.
More generally, I think it'd be nice to be able to define arbitrary snippet triggers. Thoughts?
Add exclusion filters to Application / folder search results
in Alfred Feature Suggestions
Posted
I second this, as I have the same problem with my development environment.
I also would echo this for URLs and contacts as well. I have several contact lists for various orgs that exceed several thousand entries; it's inconvenient and it's a bad system to have a CardDAV server with that many entries, but that's my reality. Nearly guarantees that I have irrelevant results on many queries. Same goes for URLs if I've pasted in URLs from the same domain (e.g., reddit.com, reddit.com/r/alfred are sorted based on most recently used, which is often not what I want). At least some option for prioritizing root domains in suggestions, or filtering out certain contact groups would be top notch.
In addition to OP's initial comment re: filtering file results.