Jump to content

Andrew

Creator
  • Posts

    4,954
  • Joined

  • Last visited

  • Days Won

    325

Everything posted by Andrew

  1. @GuiB that's correct, it's simply whitespaces at this point. This is something which will definitely change to represent a much wider range of word boundaries.
  2. @xilopaint It's extremely likely that macOS doesn't index the library caches folder, in which case, Alfred can't search metadata in that folder.
  3. @xilopaint if you have a hotkey directly to a workflow input, you get the workflow input's icon on the right instead of Alfred's icon.
  4. @surrealroad I've now made this fix, could you please let me know how you get on?
  5. @mikedvzo I actually have a ticket to implement this for when Alfred Remote is updated.
  6. @nikivi Alfred doesn't know when your script will return with results, and any change to the default behaviour will inevitably cause undesirable behaviour. Don't forget that you have full control over dynamic configuration of objects though... why not add a JSON Config utility between the hotkey trigger and the script filter to just set the titles to nothing. For example, something like this: You'll probably want to pass through the arg too... set the configuration as something like this: { "alfredworkflow" : { "arg" : "{query}", "config" : { "title" : "", "runningsubtext" : "", "subtext" : "", }, } } Cheers, Andrew
  7. It's worth adding that this may very well be a bug in macOS, as there is no reason for the target files to be marked as system - this prevents them from showing in Spotlight too. Note that this workflow operates directly on the actual shared files. I don't think the alias files are relevant in this case, in fact, I didn't even see where they were. Cheers, Andrew
  8. @Xavez I just noticed in the metadata that it's marked as a system file which Alfred ignores by default. Try this workflow with keyword 'ishare' which should find system files in the shared folder. I've tested it and it seems to work as expected: https://www.dropbox.com/s/6vmv9ofusqzb6gh/Search Shared iCloud.alfredworkflow?dl=0 Cheers, Andrew
  9. @Xavez The file you dropped in to the metadata tool is different to the alias' you show in terminal. Is this what you are seeing when you drop one of the .alias files in, or are you dragging a different file in? Alfred should find the file you dropped in as long as ~/Library/Mobile Documents/ is in Alfred's Features > Default Results > Search Scope, which it is by default.
  10. @GuiB Thanks for spotting this, I'll have it fixed for the next pre-release
  11. @Alex M try this duplicated version of the theme with lower blur: https://www.alfredapp.com/extras/theme/kVih5pkcFN/
  12. This is a known issue with certain Macs and is due to the way High Sierra deals with blur radius. To work around this issue, duplicate the frosty teal theme, reduce the transparency a little, and make the blur under 50%. What's interesting is that it only affects certain newer Macs - my low power old Mac Mini (barely meets minimum spec for high sierra) works absolutely fantastically with high blur themes.
  13. @Cra1g If you just want to run a command, why not use the Run Script action which won't open Terminal at all. If you have to open Terminal, there are plenty of ways to quit Terminal after this. The cleanest would probably be to automatically append exit to your Terminal command. Cheers, Andrew
  14. Update: I'm currently working on a generic fix, as this turns out to be a more holistic issue than framework / JSON. Shouldn't manifest itself much, but better to be safe than sorry
  15. @surrealroad sorry about the delay on this, I haven't had a dev setup on High Sierra so haven't been able to looking into this with more detail. It looks like Apple's framework or JSON parsing has changed a little, and where Alfred is expecting a string for the "arg" field, you are passing an integer. Before High Sierra, Alfred would happily take any object type and fall back onto the objects description, in terms of e.g number -1, that would be "-1" as a string. This no longer seems to happen. I'm going to look a little deeper into this and likely create a workaround or fix, but in the short term, you can fix this by returning "-1" instead of -1 for the arg. (For reference, the JSON format is here: https://www.alfredapp.com/help/workflows/inputs/script-filter/json/)
  16. @ascandroli @vitor could you please update to the b871 pre-release and let me know
  17. Ah no worries, I can see what I've done (in fettling with the match field). I'll get a new pre-release out shortly!
  18. Hmm I'm not seeing this in my test filters, but this whole area has been worked on. If you add the Script Filter getting started workflow, does it work as expected? Under what set of conditions / options in the Script filter are you seeing this issue?
  19. @surrealroad My test workflows are working on 10.13 Beta 7. Are you seeing any errors in the Alfred debugger (set to All Info), or in Console.app? Are any of your Script Filter workflows working (especially non-JS script filter ones)?
  20. @GuiB Doh, sorry 'bout that! This is why I have pre-releases I'll make sure it doesn't show anything if rerun isn't present in the next release.
  21. @GuiB Yep no probs, I've updated it to accept one or more files for the next release Also, interesting what @deanishe said - For some reason, I was fully resolving paths and symlinks on the receiving code. I've changed that to just standardise paths instead (i.e. resolve ~/).
  22. The Alfred 3.5 pre-release adds new 'browse' and 'action' alongside the 'search' AppleScript commands. Use search to populate Alfred's search field. Use browse to populate Alfred's file system navigation path. Use action to show the actions panel for the given file. Cheers, Andrew
  23. @GuiB If you update to the 3.5 pre-release, dynamic configuration using JSON should now work (the bottom one in your example workflow). Note that you could actually get rid of the ArgVar object in that flow and put the {query} directly into the value field in your JSON Config object. I still haven't gotten around to being able to use variables directly in complex tables such as the file filter fields section, but this is planned. Cheers, Andrew
×
×
  • Create New...