Jump to content

meadeiator

Member
  • Content Count

    10
  • Joined

  • Last visited

  1. Ok, deanishe, I just installed that workflow. AMAZING. Apparently this weekend I'll be looking through all of your other workflows on GitHub to see what else I've been missing out on. 🙂 Thank you, again!
  2. Thank you, deanishe. I appreciate the clarification and the suggestion! Hope you have a great day.
  3. Good morning. I've been scratching my head on this one and haven't found much on the forum, which leads me to believe I may be going about this wrong as it feels quite "simple." 🙂 Appreciative for any feedback or guidance. Use Case: I want to be able to open any folder (repo) one level below my "GitHub" folder in both Atom and Terminal. The number of folders (repos) within the "GitHub" folder changes wildly as I add and remove repos. I created a Workflow using a File Filter that limits the search to type "folder" within the "GitHub" folder. I can successfully pass the {query} result (in this case, the folder location) to both Atom and Terminal and get the desired results within each of those Actions. The Question: When using the File Filter, it is also providing me all of the sub-folders within each of the folders (repos) within the "GitHub" folder. The ideal scenario would be just to display those folders directly beneath the GitHub folder, similar to how if I open Alfred and start with "/" I can essentially navigate folders. I found some fairly old (4+ year) posts around using Script Filters to attempt and accomplish, but they were incomplete and/or didn't seem to offer workable solutions. Again, appreciative for any suggestions or guidance. The current iteration of my workflow sames me tremendous time and keystrokes and I can typically remember enough of the repo (folder) name to filter it down quickly, however, the older I get, the less I can reliably count on my memory. 🙂 Thanks in advance for any help!
  4. Nice.... That's sweet. Works like a charm. Running through all the options but so far so good.
  5. Yes. That is what produced that log. 2 or 3 attempts to nest nest.
  6. I'm not getting anything recorded to the log. Opened console but can't find anything related to Nest in there. Am I missing something?
  7. Ok, to confirm it is pulling the workflow from http://dl.dropbox.com/s/qmu1iyora9h6pr9/jc-nest.alfredworkflow I have deleted the old. For good measure, I cleaned out the volatile and non-volatile Workflow Data for jc-nest. Deleted the password from keychain. Then did a clean install. It prompts me for login information...confirms I'm all set and ready to go. On any of the commands, I see "Talking to Nest..." for about 1 second or so below the input box and the selected filter item. Then it just goes away. On the "nest nest" command it says "Finding Nests..." and then times out the same. Happy to continue and test.
  8. Very cool. Quick question. I deleted the old workflow, installed the new and when I attempt to do any of the commands it appears to attempt to connect to Nest but quickly times out and just leaves the commands in Alfred's input box. I thought perhaps I needed to refresh credentials, so I deleted the jc-nest password from keychain hoping to re-prompt for credentials again but to no avail. Just downloaded off GitHub minutes ago so think I have the most current version. Any suggestions?
  9. Let me know if I can help test it out. Happy to pitch in however I can.
  10. Love the workflow. Thanks for your time and for sharing. I'm in near Nest Nirvana...now if only I could control the second thermostat. :-)
×
×
  • Create New...