chrisWhite

Oh, duh, I'm pointing it at at the drive root that way, it's been a really long week ?

Yeah, I had picked up a little bit about the actual problems for NSAppleScript doing forum searches along the way, copy and paste is a minor thing. I just tried omitting the `.` in the icon path to make sure I hadn't originally had a typo or other error and Alfred does not show an image without it, I'm not sure whether it's an AppleScript problem however since the JSON is returning the correct path to Alfred, does Alfred care what is being executed or just what is returned back? "icon": { "path": "/icons/unloved.png" }, That makes sense about how keywords work, I hadn't thought through that entirely. In terms of duplicate keywords, yeah, there are contexts in which having multiple keywords are helpful, between Alfred, Keyboard Maestro macros, app shortcuts, Karabiner triggers, TextExpander/Alfred/Teacode Snippets and app palettes commands for Visual Studio Code, Sketch, etc. it can be hard to remember everything so being able to fallback on a general keyword, like iTunes for all iTunes workflows makes things easier and is still usually faster than consulting a cheatsheet or that workflow (though I do use it as well ?). Yes, it would be better to consolidate automation workflows but that's a constantly ongoing evolution. Thanks again, I can't tell you how much I appreciate your help!

Wow, thank you so much deanishe, your answers and pull request were immensely helpful! Regarding 1, that makes sense about variables, while I'm okay at bash scripting I'm still figuring out what information AppleScript has and what it doesn't, I figured it wasn't a full shell but didn't know if it could access some of the same information, thank you for clarifying! I agree that the Run NSAppleScript object wasn't ideal, it's where I started before switching to the Script Filter, learning a lot more and hadn't gotten back to reworking the action itself, I'm glad it looks like I would have been on the right track! Regarding items in the workflow directory, I had tried to call them using a relevant path but had missed the leading `.`, that's much easier to work with! I didn't plan to leave the code in there to allow it to be run anywhere, just did to for convenience as I was working on it but with a working relative path even that's unnecessary. I hadn't thought of using a symlink, that's brilliant! Thanks for the info on resolution, I'll try 256px and see how they look on an iPad. Regarding the last item, I had tried chaining a Keyword as input to the Script Filter like you reworked it but while it will execute the downstream action it won't trigger the Script Filter's functionality to run so I get the placeholder result rather than actual results, it sounds like I should just use duplicate script filters and running a script file limits the repeat for the most part, just hoped there might be a better approach. @Andrew if you don't mind a feature request it would be wonderful if you could set multiple keywords throughout Alfred, something like `love|itunes`, I definitely would use them for workflows and web searches so I could assign general keywords that I can arrow/number select from when I'm blanking on a specific keyword. Here's an example of where I've chosen general over specific:

I'm just getting started with creating my own workflows and I have a couple questions I haven't found the answers for yet after a bunch of searching, reading and testing. A quick note to begin with, I'm writing this partially as an exercise to improve me proficiency with AppleScript, as frequently painful as it is. It does seem like a good workflow to use it for since its functionality is almost entirely reading information from and sending commands to the iTunes AppleScript Dictionary. JXA is a little further down the to-learn list. 1. What is the proper way (if there is one) to get Alfred's workflow environment variables into an AppleScript file? Right now I'm using the Script Filter to issue the Bash command osascript *file*, I can append a variable to it like "alfred_workflow_data" and read it as an argv or use (do shell script "pwd") to get the workflow path but I haven't found a way to access all of the variables directly. I'm open to ultimately running it as a usr/bin/osascript if that's the best solution, but it's nice to just run the script from my code editor rather than copying and pasting it every time I want to test a change. I have read the pinned post on using environment variables but I'm not sure how to apply it in this context. 2. It looks like the best practice is to use alfred_workflow_data and alfred_workflow_cache where possible but is it appropriate to use the workflow folder for things like included icons or should I be creating a data directory, copying the files there and then using that location when setting icons in a Script Filter? Given that there doesn't appear to be a provided environment variable for the workflow folder path I wasn't sure if that was to discourage using that in the workflow or because it's trivial to determine that path another way. 3. I have a couple of different icons I'm using for different workflow components so I don't want them all to inherit the workflow icon but I also use some of the same icons for multiple trigger objects. If I assign them the same icon I get duplicate *iud*.png files, is there a way to set the path for the icon programmatically so I can set a single image to multiple objects? 4. Along similar lines, does Alfred allow you to use any vector formats for icons? It doesn't seem to accept SVG and it converts vector PDFs to PNG images but I know that some of Alfred's internal workflows use vector code for icons so I thought it was worth asking. If not, is 512px the appropriate resolution? I've seen 128px referenced in older threads but that seems pretty small for uses like icons in the iOS remote app for devices like retina iPads. 5. Finally, is there a good way to assign multiple keywords to the same action? I'd like to trigger my script filter with both itunes and love and I had hoped that using a Keyword object as the input to a script filter would do it but while it still lets me trigger the action object I've linked the script filter to the script filter functionality doesn't work. I've also tried adding an Arg and Vars utility to overwrite the query to the keyword for the Script Filter but I get the same result. I can just duplicate the Script Filter with a different keyword but am trying not to repeat an identical function if I don't need to. Thanks for any help, I really appreciate you taking the time to read over this. The workflow in its current state can be found on GitHub. Alfred 3.6.2 [921] macOS 10.13.5 (17F77) I've customized a lot of my macOS environment but I don't think anything that would affect AppleScript and likely not anything that would affect running osascript commands from /bin/bash.

@GuiBJust wanted to say think for this, I've been really wanting Hyper integration with Alfred for a while now and this is great!

Thanks!

This is fantastic! Thank you so much, I've really wanted a better way to interact with DEVONthink in Alfred, way better than just setting up a custom search! As an aside, I really like the Alfred theme you're using, any chance you could post it?

This is exceptional @xilopaint, thank you for building it!

It's a pity that you have to have a token, I requested one on a couple of my Slack groups to mixed results and there are two that have them entirely disabled. Would oath work with any Slack channel or still require manual authorization?

I had missed that, thanks for pointing it out, I'll try moving it back into Dropbox but out of the Apps folder. So that's why the Apps folder was grayed out, I remember having to do a ⇧⌘G to get to it, I guess I should have taken the hint. Thanks!

Sorry Andrew, I got really slammed on a project and haven't had time to play with this again until today. I tried moving it out of Dropbox and Alfred seems to be working fine now but it's also possible something else may have changed on my system since I had previously restarted Alfred. I seem to be good but I'm not if this gives you much certainty in Alfred on El Capitan. Thanks for the help!

Yeah, I don't see any repair permissions feature in Disk Utility unless it's built into the 'First Aid' feature. I went ahead and run this: cportable:~ cwhite$ chmod -R u+rwX,go+rX ~/Library/Application\ Support/Alfred\ 2/ cportable:~ cwhite$ xattr -rc ~/Library/Application\ Support/Alfred\ 2/ cportable:~ cwhite$ chmod -R u+rwX,go+rX /Users/cwhite/Dropbox/Apps/Alfred cportable:~ cwhite$ xattr -rc /Users/cwhite/Dropbox/Apps/Alfred No difference, Alfred is still reseting on restart. I guess this would be a good time to finally reprogram my muscle memory to use Alfred default hotkeys instead of my old Launchbar ones

First, to be clear, I know El Capitan is in beta and I do not expect you to support prerelease software. I'm sure that it's crazy annoying to get flooded with support requests for something that isn't stable and hasn't even been released yet. With that said, I am experiencing a problem with Alfred on El Capitan and wanted to offer any assistance in troubleshooting if it can be of any assistance to you. The issue I'm having is that any time I exit Alfred and restart it Alfred seems to lose most of it's settings. Every time I restart it looses settings like custom hotkeys, search scopes, custom searches, themes and advanced appearance settings all seem to be reset to the defaults. However, workflows, sync folder, Powerpack license and usage are all carried over just fine. It doesn't look like /Users/cwhite/Library/Application Support/Alfred 2/Alfred.alfredpreferences is getting updated while exiting or relaunching, the last change time was from this afternoon before I updated to El Capitan. Setup notes: I did an update install from Yosemite. I am on Alfred 2.7.1 (387). With the exception of iStat Menus everything I've tried this evening since updating has worked as expected though I did have to re-enable some apps to launch at startup. If I can do anything to help please let me know how, otherwise keep up the incredible work you do on Alfred! Thanks

It works on the current semi-public beta as well. I'm loving it, Alfred feels like it fits perfectly now!