Andrew Posted October 1, 2014 Share Posted October 1, 2014 Hi All, I want to make a little behavioural change for [script] input filters where you have a keyword defined as with space, argument optional. I essentially want to prevent an unnecessary second re-run of the script with argument '' when typing the space following the keyword. Here is what currently happens if you have a keyword 'fruit' set as with space, argument optional. - Type 'fruit' into Alfred, script is run with arg '' and relevant results are shown. - Type 'fruit ' into Alfred, script is run with arg '' and (I expect) the same results are shown. - Type 'fruit a' into Alfred, script is run with arg 'a'. With the change, the behaviour would be... - Type 'fruit' into Alfred, script is run with arg '' and relevant results are shown. - Type 'fruit ' into Alfred, script isn't run again as arg is the same. - Type 'fruit a' into Alfred, script is run with arg 'a'. Question: Does anybody have a workflow or know of a workflow which would be affected by this specific case, or the case where Alfred prevents re-running the script if the argument is unchanged such as the example above? Cheers, Andrew Link to comment
Carlos-Sz Posted October 1, 2014 Share Posted October 1, 2014 I made and used a lot of workflows and I don’t know any that would be affected by this change. Link to comment
Andrew Posted October 1, 2014 Author Share Posted October 1, 2014 I've popped this behaviour into Alfred 2.5 b296 pre-release... if people wouldn't mind updating to the pre-release and checking that their workflows still operate as expected, I'd very much appreciate it Cheers, Andrew Link to comment
Florian Posted October 1, 2014 Share Posted October 1, 2014 I had only one workflow in mind that could have had a problem (because it was using the first step to launch a php server so that all subsequent queries would trigger faster). No problem with the latest 296 update. :-) Link to comment
Carlos-Sz Posted October 1, 2014 Share Posted October 1, 2014 I have just updated and so far so good. Link to comment
rice.shawn Posted October 2, 2014 Share Posted October 2, 2014 If anyone coded a workflow that would be affected by this change, then that would be strange. I can't imagine a real, practical difference between a null argument and a whitespace argument with anything that I've seen here. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now