Jump to content

mmcduffie

Member
  • Content Count

    20
  • Joined

  • Last visited

  1. Thanks for the reply Andrew. Unfortunately I don’t have a clear recollection of when Alfred’s sort order for bookmark results stopped working for me. It’s been this way for months. I cleared data (history/cache?) losing my other preferred top items history (apps, etc.) a couple of months ago but it did not resolve the bookmark ordering issue for me. I can’t remember exactly when everything went sideways for me (sorry, not helpful I know). I remember the new caching and the reading list results but I could live with it. I switched to Chrome as my default browser this year and started adding bookmarks accordingly after Apple nerfed extensions the last time (or maybe the time before when they required a paid developer account causing several developers to abandon Safari). Basically some my most used extensions were on borrowed time and 1 or more quit working. I vaguely remember the correct bookmark as top item up until a few months ago when it stopped working either after a system/Safari update or an Alfred update. So it’s likely I’m misremembering it happening with the new bookmark implementation. I had forgot Chrome bookmarks were not included before so it’s likely that my issue is not related to the caching change. Not helpful I know but after trying clearing my history I just lived with it. I’ve checked to make sure I’m on the lasted version of Alfred. I’m also up to date on macOS High Sierra (I hate new capitalization scheme. Mac really is second class citizen to Apple). Any my ideas on resetting, etc. would be greatly appreciated since my setup is evidently not working as designed. Thanks, Mike
  2. I'm sure there's a technical reason why Alfred changed the way it handles bookmarks in searches, but the new method is a significant regression for me. Previously I could type the partial name or domain of a bookmark and the relevant Safari and Chrome bookmarks would display with the most used one as first item. You could force first item by re-running the query and selecting the desired item a few times. 1) Now Safari bookmarks are always listed first even though I use the Chrome bookmark more often. Chrome is set as the default system browser, so it makes no sense for Safari bookmarks to always be listed higher in the default results even without the most used order sort. I greatly prefer the old method where the most used item is first since I use Safari for some sites and others in Chrome on the Mac. I can't remove the Safari bookmarks as I use the synched Safari bookmarks in iOS where there is no real browser choice (re-skinned webkit only). 2) The new mechanism also displays Safari Reading List items (which I have too many of and use differently than standard bookmarks) along with the bookmarks results flooding the results with unwanted noise. I have used an add-on workflow/keyword for years to search the Safari Reading List separately so this is not desirable for the way I use Alfred. There doesn't appear to be an option to exclude Reading List items from default results if you include bookmarks. At least I can't find one. The Reading List items are often higher than the Chrome bookmark that I repeatably select. Again the results sort order never reflect usage with the new bookmarks mechanism. I'm running the latest version with Power Pack. Is there something I'm missing or is this broken for everyone since the bookmark handling change earlier this year? Thanks
  3. Thanks Carlos, but I found the issue. Long story short: I had the defaults (all) for escaping and the escaped path string was stopping the script from executing. Unchecking the escape options made the workflow work as intended. Long version: My keyword test input was only working because I had didn't use a real path with forward slashes, etc. When I used the copy clipboard test results from the File Filter as the input for the keyword (e.g. /Volumes/Data SSD/Downloads/!Sorted/!Icons/test icon-ai.zip), it failed as well. Again the first line of the script is a test notification, so I know the script never ran. My other workflows don't use file paths, so I never ran into this corner case. Again, I could work around it by using Run NSApplescript instead of an embedded script, but I wanted to understand what was failing. Maybe this will help someone else as well. Thanks again to everyone who responded.
  4. Thanks for the feedback, but the new code only works when triggered by a keyword and fails to trigger from File Filter (same as original posted code).
  5. Thanks for the feedback, but that's what I'm currently doing to make it work: "Copying the applescript to a NSAppleScript action (triggered by the File Filter) works as well" I'd like to understand why this isn't working. Additionally, I have to edit and debug n Script Editor; then copy to NSApplescript action. Alfred NSApplescripts are also limited, e.g. cannot have subroutines/functions. So I prefer to use embedded scripts. What's confusing is that this exact setup works in other workflows for me. I remember it working here for a while triggered by File Filters. I've tested: File Filter → large type (works for passed query) File Filter → open file (works for passed query) Keyword→ Run script quoted above (works for passed query) but File Filter → Run script quoted above (fails). Doesn't even trigger the script as the first script statement is a test notification.
  6. Does anyone have idea why a Run Script action (/usr/bin/osascript) will not execute from a File Filter trigger? I could swear this was working earlier. Trying to override the search in spotlight function with an applescript to parse the filename to a more usable form. Applescript runs fine as standalone or if triggered by keyword in the workflow. Copying the applescript to a NSAppleScript action (triggered by the File Filter) works as well, but I prefer an embedded script. I'm using the same Run script I've used in other workflows (and it works if triggered by a keyword in this workflow): run script (POSIX file ((do shell script "pwd") & "/find-in-spotlight.scpt")) with parameters {"{query}"} Yet no matter how I link it to the File Filter it doesn't execute.
  7. Thanks for the fast response. I think I use all your workflows now, they're really well made. Someone else asked above but are you considering releasing the source of the embedded binary? I enjoy learning how these are made. It's educational to see a well designed workflow.
  8. Excellent workflow. Thank you. Would it be possible to add a delete function for items?
  9. DOH! I looked right at that and then forgot all about it as I focused on my expected behavior of the Removable Media vs Local Volumes. Thanks. I knew I needed more coffee today.
  10. Did some quick testing and it appears the Removable Media setting is designed for thumbsticks and not USB hard drives. Also selecting the non-system internal drive produces an error dialog that the volume is busy. While not elegant it may meet the WAF (wife acceptance factor).
  11. I'm not sure what the proper etiquette is here, some forums are rather sensitive about thread highjacking, so apologies in advance. My problem is similar enough to original post that continuing the discussion here seems easiest. I'm seeing similar issues in both Alfred 2.4 (279) and 2.5 (295) beta. It appears the detect removable volumes logic isn't working or I don't understand the intent (small thumbdrives only perhaps?). One or more USB drives attached and mounted. Displayed in Finder sidebar as ejectable. Alfred eject command finds no volumes and fallback to files/folders/etc with eject with "Removable Media" selected in the system eject command preference. Changing eject scope to "Local Volumes" will work but lists non-system internal volumes which is not ideal. I would prefer this be spouse proof and my wife would be lost if she accidentally ejected her internal Data SSD. Is the feature "working as designed" and I need a workflow for my use case? Thanks.
  12. To give focus to the admin password dialog add this line before the do shell: tell current application to activate
  13. I figured it out. I have to check "with space" to have the two filters act as desired. I'm assuming before the fc was used regardless of which I typed. Thanks for the feedback and assistance.
  14. That appears to be the issue (similar filter filter keywords). The file version uses fc & the folder version uses fcf. I changed the folder keyword to something completely different and it works as expected. As the filters use a space, I would assume "fc name"and "fcf name" would be unique. Is this a bug or am I just expecting too much? Keyword ffc works as well but is not as much of a mnemonic for me. Turning off fuzzy matching didn't help. Thanks, Mike.
  15. I have no problems with the files filter for individual file types working as expected. Only "file filters" for folder only. Are you saying you have a filter that only shows folders? Thanks.
×
×
  • Create New...