Search the Community

My preferred way to search Google is to limit results to the past year. To do so I use this URL: https://www.google.com/webhp?cr=&tbs=,qdr:y I have attempt to enter that in the "Search URL:" field in Alfred's Preferences so that I could search within Google using that time limit just as I do on a new web tab. However Alfred's response when I click the "Lookup" function is an invalid search. The URL in the dialog box is cut off after the "/webhp" just at the question mark. I have attached a screenshot as illustration. Can anyone provide guidance as to how to use this specific Google search URL as a Custom Search? The intent is so that when I enter a term into Alfred's search field this Custom Search URL would appear as the default search. Then when I hit Return it would enter the searched term in Google's search field and activate the search just as it does for the standard Google URL. Thanks in advance for any guidance you can offer.

This is a limit imposed by UNIX, not Alfred, but the error message shown is slightly confusing, and there should be a way to overcome this issue. Right now, selecting more than exactly 260527 characters on my system and using it in an Alfred workflow (with the Argument:'selection in OS X' setting) as "{query}" will throw an error. You can see your system's bash argument character limit with: getconf ARG_MAX Alfred should allow a way to pass the selection as stdin instead of a quoted and escaped string, otherwise there is no way around this hard limit, and Line-Counting workflows, etc. are useless for larger bodies of text. ^ Confusing error message when selecting too much text. ^ A workflow example that would trigger this. echo "{query}" > .wordcount echo "Characters: "$(wc -m < .wordcount)" Words: "$(wc -w < .wordcount)" Lines: "$(wc -l < .wordcount) rm .wordcount

A lot of workflows are made to work with specific applications. It would be great if you add an option to limit workflows actions to work only with indicated apps or to exclude some apps that we don't want WF to work. This brings two main benefits especially for workflows based on hotkeys: you will not trigger some workflow by incident in other app that is not supposed to work (which could cause some strange behaviours, if for example workflow triggers some others keyboard shortcuts through AppleScript). you will be able to use same shortcuts in many applications that triggers specific workflows for indicated apps.