deanishe

Member
  • Content count

    2,788
  • Joined

  • Last visited

  • Days Won

    150

deanishe last won the day on March 21

deanishe had the most liked content!

4 Followers

About deanishe

  • Rank
    Advanced Member

Contact Methods

  • Twitter
    @deanishe

Profile Information

  • Gender
    Male
  • Location
    Essen
  • Interests
    Python, beer

Recent Profile Visitors

6,803 profile views
  1. I was under the impression that Alfred sometimes drops queued actions on the floor if an earlier actions is still running. Just tested and I was wrong. I didn't look at the workflow you posted because I was on my phone earlier.
  2. I don't think it works quite like you imagine. When your script is running, I don't think Alfred queues subsequent calls. Or rather, it does queue them, but doesn't run all subsequent calls, only the last one. Like if I search for "sandwiches", Alfred will run a query for "s", and when that finishes it runs another query with the latest input at the time the first run finishes, perhaps for "sandwi". It does not queue and run the script for all the intermediate queries ("sa", "san", "sand" etc.) because that would be bonkers. As such, I think you might have to manage your own queue (and make sure your script capturing the input in Alfred returns immediately, or it won't be callable).
  3. Has something changed? You had exactly this same conversation 4 years ago: TL;DR: NSTask normalises strings.
  4. AKAIK, there are plugins for Outlook and MailMate. The latter is my email client of choice.
  5. It is, as you say, a limitation of webmail. There is a standard method, supported by almost every email program, for addressing an email. To be able to send attachments, however, requires a custom plugin for the particular email program you use. Which in turn requires the program to support that kind of thing in the first place.
  6. telling an application can cause it to take focus, especially telling it to quit, as many apps show confirmation dialogs. So it's possible that the problem is the frontmost application changing while you're looping through the processes. Try first making a list of the applications you want to quit, and the looping over that list to do the telling: set quit_list to {} repeat with i from 1 to (number of items in process_list) set this_process to item i of the process_list if this_process is not in white_list then if this_process is not in the frontmost then set end of quit_list to this_process end if end if end repeat repeat with this_process in quit_list tell application this_process to quit end repeat
  7. Probably best to drag your backup folder into Spotlight's Privacy pane in System Preferences. That stops Spotlight indexing the folder at all, so your backup files won't show up in Spotlight or Alfred.
  8. LaunchBar extensions aren't as hard to build as that — the GUI takes care of a lot of the boilerplate. You can't do anything without coding, though. Control flow (i.e. run this script next) is controlled via script feedback, so it doesn't have the arbitrary limitations imposed by Alfred's requirement that control always returns to a GUI workflow element. LaunchBar's feedback format is also richer and is a tree, not a flat list, which makes drill-down-style workflows a much better fit. No faffing around with delimiters or the dead-end External Trigger UX: Go Back is a native action. But yeah, you can't do very much (add web searches?) without coding. Personally, I prefer LaunchBar's workflow/action model, with the caveat that I've only built one Action for it (a copy of my git repos workflow for Alfred). I never got comfortable with LaunchBar's UX, however. I like Alfred's normal text box input.
  9. Because it does matter sometimes. Comparing a user's query to filenames is far more common than a workflow that needs unnormalised input. He means as a way to pass input around so Alfred doesn't normalise it. For a Script Filter, I think the clipboard (i.e. pbpaste) is the only way to get your input past Alfred's filters.
  10. @rhyd I think David's chaining technique is out of date. It's for Alfred 2, which didn't allow you to connect Script Filters together. Alfred 3 does. Simply drag a connection from one to the other.
  11. It's generally symptomatic of OS X's preference for NFD-normalised UTF-8 text. See what I mean? Because OS X prefers NFD. How else would such a command be run? AFAIK, it all goes through NSTask. It still goes via NSTask. Nah. Normalisation is a sensible default. I wish more platforms did it. 99% of the time, you're interested in the characters that make up a text, not the codepoints/bytes that represent them. I mean, who the hell else but a programmer cares whether "ü" is represented as "ü" or as "u+¨"? OTOH, everyone expects the two to match. Users couldn't care less about normalisation or bytes.
  12. It probably isn't Alfred. In this case, it's likely NSTask, but OS X fundamentally prefers NFD (which all HFS+ filenames are normalised to). Why? I know naff-all about Asian alphabets, but I'm having trouble understanding why OSX should return the composed Unicode form, not the decomposed one.
  13. Except that doesn't work at all in many cases. @Andrew, you do exactly the same with Alfred workflows. info.plist has to be in the workflow's root directory, so there's literally no way to create a File Filter for the workflow that includes important files like info.plist or icon.png but excludes the folder with all your 3rd-party libs in. TL;DR: Can we please stop pretending that, with sufficient workarounds, Alfred can handle "everything but X" situations? It really can't.
  14. Because it's not reasonably possible to keep re-running the workflow until it produces a random password of precisely the right length.