Andrew
-
Posts
4,926 -
Joined
-
Last visited
-
Days Won
316
Content Type
Blogs
Gallery
Downloads
Events
Profiles
Forums
Articles
Media Demo
Everything posted by Andrew
-
The template (off the [+] button > Templates > Files and Apps > Launch file group from keyword) will create the workflow for you, then you just need to fill the details in. Let me know if you need any help with this
-
Did you try the "Launch file group from keyword" workflow template? This should help you out.
-
That's actually already fixed in b187 if you update to the latest pre-release
-
Great! Thanks for finding and testing this for me
-
Update to pre-release b187 and that should now be fixed
-
Ah D'oh! I can totally see why this is happening! I need to escape backslashes in the string before escaping anything else otherwise all the other escaping gets escaped. I'll fix this in the next hour or so... thanks for spotting!
-
AppleScript can be a bit funny, and blocking... It's very likely that you'd get the same hanging behaviour if you run this same script in AppleScript Editor. There doesn't look to be anything wrong with the script, so it could just be Mail.app being rubbish! It might be worth commenting out the set mailbox line (prefix with --) to see if that's the line causing the issue instead of the selection.
-
'gc' should match Google Chrome for either setting. Try updating to the pre-release as that captures fuzzy matches like this even before Alfred has them cached.
-
The option in Alfred's prefs only refers to the file navigation mode. In Alfred's default results, use cmd+down to navigate into that folder [moving to help subforum]
-
This is for a few reasons, both security and to prevent overwriting currently used hotkeys. You have a few options, but the easiest thing to do is to is just setup syncing between your two Macs, then everything will happen magically
-
I've created a small command line tool which should hopefully help you re-normalise any strings: https://dl.dropboxusercontent.com/u/6749767/Alfred/normalise.zip If you include this in your workflow itself, you should be able to run it directly like this: usage: ./normalise -form NFC й You can add -verbose after NFC to see what is happening, or no arguments to see the options. Let me know if that helps at all
-
That's great to hear!
-
Should be fine, but the point in the pre-release is for users to let me know if there are any issues
-
Unless I've misunderstood what you are looking for, you should just be able to use cmd+c on the selected item in Alfred to copy the path for that item Edit: Ahh I see you mean copy the finder items paths. That AppleScript should work too if you put it in a workflow Run Script action (osascript) attached from a hotkey.
-
Thanks! Hopefully somebody can chime in to help too -
It may be that Parallels VM doesn't see the simulated cmd press then (quite likely)
-
You may want to add a kMDItemTextContent field in the Advanced prefs if you want to search contact content too
-
Ah my apologies... give this workflow a go then: https://dl.dropboxusercontent.com/u/6749767/Alfred/Workflows/Contacts%20filter%20like%20v1.alfredworkflow
-
I get the impression you aren't finding contacts at all in Alfred (which is different to the reported issue above)... am I right? If so, did you answer "no" when OS X asked if Alfred could have access to your contacts?
-
I'm not sure as I would have assumed that sed would be happy with decomposed unicode. You could maybe strip the accented characters first using iconv? http://stackoverflow.com/questions/9889428/unaccent-string-in-bash-script-rhel
-
haha oops!
-
Yep, Tyler is correct with this! [Moving out of bugs to help forum]
-
Bash script in workflow. Language of locals ? Accented characters ?
Andrew replied to hubertcampan's topic in Closed
I've replied to your previous thread - not sure how that one got missed. Going to move this to closed to keep Alfred's bug thread focused. -
I wonder if this could be a consequence of decomposed unicode. Alfred uses NSTask which automatically normalises and decomposes: http://en.wikipedia.org/wiki/Unicode_equivalence#Normalization Could this be the issue?
