Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


kejadlen last won the day on March 1 2018

kejadlen had the most liked content!

About kejadlen

  • Rank

Recent Profile Visitors

351 profile views
  1. Just FYI, since forecast.io is becoming darksky.net, I've changed forecast.alfredworkflow accordingly to dark-sky.alfredworkflow: https://github.com/kejadlen/dark-sky.alfredworkflow https://github.com/kejadlen/dark-sky.alfredworkflow/releases/tag/v2.0.0 The only change needed (assuming I didn't screw up the transition) is moving from FORECAST_API_KEY to DARK_SKY_API_KEY after updating the workflow.
  2. It's a side effect of switching to Alfred 3 for this particular workflow. Other workflows might handle it better, but it would've been a lot of pretty complicated work for a problem that's pretty easy to manually fix. Released 1.0.8 which goes to the right day: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.8
  3. D'oh! Getting my process working with the new environment variables has been somewhat hairy. Released 1.0.7 which should now properly include the vendored dependencies: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.7
  4. Thanks, LiamW! Revoked those keys and fixed the issues you pointed out in 1.0.6: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.6
  5. If you're like me and keep your workflows in public git repos, I wrote a helper for keeping workflow environment variables set to "Don't Export" out of your git repository: https://github.com/kejadlen/filter_alfredworkflow This uses git's built-in clean/smudge feature to rewrite the info.plist file before it enters the staging area. Instructions are in the repo README.
  6. FYI, I released 1.0.5, which adds support for Alfred 3 by using the built-in environment variable support for API keys: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.5
  7. @LiamW The wrong ordering is a bug in the workflow - I'll fix that in the next release. If you select one of the options, Alfred will remember that and move it higher up in the list.
  8. Definitely planning on it, but no timeframe since I don't know when I'll be able to get around to it. Anything in particular you're thinking of as far an update for Alfred 3? The only improvement on my radar at the moment is switching from my hand-rolled configuration to using the built-in one.
  9. Well, that was pretty silly of me. I'll put the version somewhere in the next release. The latest versions of this workflow should have "config-forecast" instead of "forecast-config". If you're still seeing the latter, can you try deleting the workflow and installing the latest one?
  10. I released 1.0.3 to address some bugs around initial config that should hopefully address some of these issues: https://github.com/kejadlen/forecast.alfredworkflow/releases
  11. @Amator: Do you know what version of the workflow you're using?
  12. The only thing you can do for now is to open the debug pane in the workflow in Alfred and see what that says - I'm working on adding better errors to the workflow, but am pretty busy at the moment.
  13. I'm not sure why your keyword is "forecast-config" then... it should be "config-forecast", and the icon should look different.
  14. Looks like you're using a pretty old version of the workflow - try updating to the latest? https://github.com/kejadlen/forecast.alfredworkflow/releases/download/v1.0.2/forecast.alfredworkflow
  15. Hey all, I whipped up a quick workflow for searching Giphy: https://github.com/kejadlen/giphy.alfredworkflow/releases/download/v1.0.1/giphy.alfredworkflow On selecting a search result, the gif is downloaded and previewed using Quick Look while a direct link to the gif is copied to the clipboard.
  • Create New...