Jump to content

phyllisstein

Member
 View Profile  See their activity

  • Posts

    366

  • Joined

  • Last visited

  • Days Won

    7

 Content Type 

Everything posted by phyllisstein

  1. phyllisstein
    Hm. I've changed it to use the built-in unzip utility (I think), but I now can't do much error-checking with it. See if you have any luck, though.
  2. phyllisstein
    Hm, it doubly shouldn't be doing that because codecs isn't in the file anymore and there's nothing on line 20. I just redid the upload by hand in case my rsync daemon is acting up—one more thing to check!—so try http://alfred.daniel.sh/Workflows/Alleyoop.alfredworkflow
  3. phyllisstein
    I just pushed an update that should address the "Invalid control character" thing. Autocomplete entries in the file often included tabs, which the JSON decoder didn't like. Figured it out once it started breaking on my own machine. Give the new version a shot; it should be accessible through the download link above or Alleyoop.
  4. phyllisstein
    Whoops, dumb. Changed everything but the actual downloadable file. It should be there now.
  5. phyllisstein
    I could try that, but communicating with the zip process might be even more of an annoyance. I just pushed one more update; would you mind trying that as well? Meanwhile I'll look into using zip.
  6. phyllisstein
    Hah, that's just where I was checking. That's likely to be the problem. And since it's internal to the module and hidden in the zip file, I don't think I can just pass it through to the UTF-8 encoder/decoder. You may need to rename them, but that's not really an ideal solution. I just pushed an update that may help—give it a shot and see if it works any better.
  7. phyllisstein
    That's terribly strange. It'd be great if I could take a look at the workflow; it looks from the traceback it's finding a non-ASCII character in one of the files in the zip, maybe, but I'm not totally sure how to fix that.
  8. phyllisstein
    Does your workflow name or path have a "`" accent in it somewhere?
  9. phyllisstein
    Dammit, I thought that was fixed. Probably so. I'll look into it more.
  10. phyllisstein
    No pain at all. Are you using ST2, or ST3? The last time this problem cropped up it was because somebody's Package Control installation had inserted some character that caused the notoriously finnicky JSON loader to choke. The guy solved it by deleting every occurrence of that character, but I still don't know what it was. It'd be most helpful if you could e-mail me (d at daniel dot sh) your Session.sublime-session file, so that I could fix this permanently; otherwise, delete the character it's complaining about and you'll be fine. The file is in ~/Library/Application Support/Sublime Text 3/Local/ or ~/Library/Application Support/Sublime Text 2/Settings/. The path thing isn't there anymore because I doubted that it was useful and rearranged the workflow; I could probably find a way to put it back if you wish.
  11. phyllisstein
    Not to worry! As I said, only Alleyoop can't update itself, since its script would be doing the update. You have to actually open the file it downloaded and let Alfred overwrite the old copy. With other workflows, this doesn't happen—they'll be transparently updated without your doing anything else.
  12. phyllisstein
    Oh, goodness, you're absolutely right; I see where the confusion came from, now, and I've corrected the problem. I wired the "oop?" script filter to post a notification and it totally shouldn't have. If you want to update one workflow, just enter "oop" (and, optionally, a search) and you'll get a list of workflows with available updates. For example, if you enter "oop" right now, you'll be told that Alleyoop has been updated. Select it from the feedback list and hit Return, and an Alleyoop.alfredworkflow file will appear in your Downloads folder. (Normally, it automatically extracts and replaces data in the workflow folders, but it can't do that for itself.)
  13. phyllisstein
    Great! That's the expected behavior. "oop?" lists every workflow that supports Alleyoop, and its most recent update, whereas "oop" checks for new updates. We can keep testing to see if individual updates are still broken, if you'd like, or we can take it as read that it's working.
  14. phyllisstein
    Hey fellow workers of flow! Sorry to resurrect an old thread, but I'm sort of curious to know how alp is working out for people. I've been a little shocked and overwhelmed by the response—it currently has nearly 60 watchers and a few forks on Github—so I wanted to touch base. It seems like it's stable as of now, meaning that I've used just about every feature in one or another of my own workflows without bumping into errors, but I wonder if there are other problems left over. Anything from bugs to inefficiencies, there's never a bad time to report them (or, better yet, submit new code on Github). And, failing slash on top of that, I'm interested in compiling a list of workflows that use alp for the Github repo and its section on my Alfred page, so if you've found it useful, let me know here, via PM, or at d at daniel dot sh and I'll add links to your work everywhere I can. Thanks for the support and help, folks. This is a cool little community that's coalescing here.
  15. phyllisstein
    Awesome! Glad to see other options for standardizing workflows. I like the rescue feedback idea—mind if I take a look at how you did it and see if it can be Pythoned?
  16. phyllisstein
    So you're getting a notification but no log file?
  17. phyllisstein
    Sure. But because I see this as sort of a fringe case and because I don't want to muddy the workflow with a user-visible settings interface, the setup is going to be a little complex. You'll have to run a search once to create the file ~/Library/Application Support/Alfred 2/Workflow Data/com.danielsh.alfred.its/settings.json. That file should contain an empty JSON object. You just need to add the key--value pair "affiliate_string": "&partnerID=2003&tduid=NL1380330" and your affiliate information will be added to the links that the workflow generates. Other users can of course do this as well, with their own affiliate strings.
  18. phyllisstein
    The first thing I'd try is grabbing the latest version and seeing if it works any better. Use the same download link in the first post. If it still fails, it'd be helpful if you could change the "Run Script" workflow item to python act.py {query} 2>&1 | tee act.log and let me know what the file act.log in the workflow folder says after you try updating Evernote. Whoops, it should've been doing that, but adding "oop?" temporarily messed it up. Uploaded a changed version. Terrific! Glad it's working for you.
  19. phyllisstein
    That's terrific. I had a presentiment that this'd be a stopgap measure, but it was just a morning's work to set up, so. Speaking of, there's another bugfix version uploaded that fixes its self-updating behavior. And with that, I think things are stable.
  20. phyllisstein
    Right you are—embarrassing typo in the Python. I've uploaded a new version.
  21. phyllisstein
    Done and done. I've been doing housekeeping all afternoon, so I just made a few quick changes and it's set. See the first post in this thread for a new download link.
  22. phyllisstein
    I've updated this workflow so that it now searches in three ways: the Mac App Store with the keyword "app," the iTunes Music Store with the keyword "its," and the iTunes Store's iThing apps with "iph." Previously, results from iThings were crowding out Mac App Store results. It also now supports Alleyoop and alp.
  23. phyllisstein
    Great work with the oAuth stuff. Gives me a nasty headache, personally.
  24. phyllisstein
    Thanks! I've updated the original workflow so that entering "oop?" will list all compatible workflows. I've also made it compatible with itself, after a fashion: you should now be able to download updates to Alleyoop from within Alleyoop, but they'll show up in your Downloads folder and have to be installed manually, since the script's files can't be overwritten while the script is running.
  25. phyllisstein
    Just a heads-up that I've totally rewritten this workflow, and made some major changes. In addition to being Alleyoop compatible, it now handles things like commas and UTF-8 characters in database and group names much better, runs much faster, and generally stinks a lot less. You can download the updated version at the link in the first post.
×
×
  • Create New...