Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by sklr

  1. It seems that clipboard picks the frontmost window for the previous application on the main screen, rather than the window that had focus when the clipboard was triggered. To reproduce (with latest Alfred and Yosemite): 1. On a laptop with an external display 2. Open iTerm, with windows on both the internal and external displays 3. With focus in the iTerm window on the non-main display, trigger clipboard and select a snippet 4. The snippet is incorrectly pasted into the front-most iTerm window on the main display; rather than the iTerm window on the secondary display that had focus.
  2. Most of my email is dealt with using mutt on a remote server over ssh. I'd like to be able to easily paste an email address into my terminal window to use when composing mail. Obviously I can already paste a simple address along the lines of foo@example.com. However, I'd really like to be able to use "Foo Bar <foo@example.com>". Would it be possible to either a) Add this as an option for copying email addresses from the alfred contact browser, or Enable multiple fields to be passed to contact actions. This would enable me to build my own workflow to stitch the fields together into whatever format I want. I could imagine this option being useful for other workflows that revolve around doing things with contact data in context -- sending someone a phone number and a name together for example. Cheers!
  3. Hi, Currently, script filters are stateless -- if one takes an argument, the filter script gets called after each letter is typed in order to regenerate the suggestions list. I've got a few cases where the full list of possible suggestions is known regardless of input, but the list is large and I'd like to allow the user to narrow down the options by typing more letters. For example, I have a script filter 'foo' that returns options ['bar', 'baz', 'quux']. As soon as the user types 'foo b', that should be reduced to ['bar', 'baz'], etc. Of the two ideas I have involving this at the moment, the first has all of its data generated locally. Therefore, I could update the generation script to take another parameter to filter results by without too much pain. However, the second workflow gets its data from a JSON webservice. The webservice isn't really designed for autosuggest, and is way too slow to consider calling it after every character. Because of the stateless nature of filters, if I wanted to make this workflow useful I'd have to deal with caching request data somewhere, expiring the cache, filtering results, etc etc. Do-able, but painful. Would there be any value in a new type of script filter that accepts a single long list of items, each of which is valid, and then deals with allowing the user to narrow down the selection by additional typing without needing to call out to the original script again?
  4. Hi guys, Really enjoying having a play with the new workflows! I was wondering if /bin/zsh could be added as an additional interpreter? It's as 'baked in' to the system as /bin/bash is, but provides what I find to be more powerful features. Thanks!
  • Create New...