Jump to content

demattia

Member
  • Posts

    8
  • Joined

  • Last visited

Posts posted by demattia

  1. Could you try manually adding in the path to the preference panes to the search scope...

     

    /System/Library/PreferencePanes/

     

    It was already there, but I removed and re-added it and now Displays shows up again. I should note that I had also rebooted, so I can't say for sure which of these actions cleared the issue, but there's apparently something there not quite working as it should.

  2. I'm having the same issue with system preference panes. Just noticed that Displays can't be found by Alfred after upgrading. Haven't noticed any issue with other panes or any applications. Spotlight finds Displays just fine. Search scope seems fine, and as I said Alfred finds all other preference panes without issues, this seems isolated to Displays.

  3. Maybe I'm missing something but the quick test I put together for this seems to work fine. I created a workflow, added a keyword that requires a parameter, then added a Run Script item. I left the language set to bash and set the script to..

    open "http://{query}.google.com"
    

    This works just as expected. I'd be glad to help you but I need a little more info so I can try to figure out what your doing and where I'm setting it up wrong.

     

    Thanks

    Yes, you're missing a vital part of it, which is where things stop working for me.

     

    I have a keyword, mmc, that requires a parameter. This get sent to a Run Script, which performs a curl and then outputs the {query} back, which is sent to  an Output Run Script and a notification. The notification works just fine, but the Output Run Script behaves very weirdly. If I send the full URL to the output script, then open {query} works fine, but if I try to construct the URL by doing open "http://{query}.domain.com" then it doesn't work.

  4. Hi,

     

    I have a pretty simple question that I can't seem to find an answer to. Hope someone here can shed some light on the situation.

     

    I have a super simple output script with the following line:

    open http://{query}.domain.com

     

    The query is something like my_sub (which I've validated with a post notification where it works just fine).

     

    The problem is that the browser tries to open the url as only my_sub, and if i put quotes around it, ie:

    open "http://{query}.domain.com"

     

    Then nothing happens at all. As an added note, the following command, just before the other one, also works fine in the output script:

    open -a "Sublime Text 2" /Volumes/dev/{query}/

     

    Thanks,

    Johannes

×
×
  • Create New...