Jump to content

Gary King

Member
  • Posts

    94
  • Joined

  • Last visited

Everything posted by Gary King

  1. Have you ever seen a case like this before? Is there anything I can do about it? I have a decently powerful Mac, considering its age of a few years. It's got an i7 CPU, 16 GB of RAM, and an SSD. This issue I'm experiencing happens every time I create a new .code-workspace file; the metadata seems to take a few minutes to populate. The issue is related to waiting for Spotlight to provide metadata for new files, right? I just created a new text file, and I checked its metadata 1 second later; there's no metadata. But 2 seconds later, there's metadata. So that seems fine. But if I do the same with a .code-workspace file, then it still takes a few minutes to populate its metadata. Is there something wrong with this particular type of file? How would I fix that?
  2. Hello! After several years, I still have this problem. I've run `mdls` to inspect one file that does not appear in a File Filter, and another that does. The file type I'm filtering for, in the File Filter, is `dyn.ah62d4rv4ge80g55eqy01s55wrr31a2pdqy` (which corresponds to the file extension of `.code-workspace` for VS Code workspace files). The `mdls` output for a file that appears in the results is: kMDItemContentCreationDate = 2018-03-26 01:00:14 +0000 kMDItemContentCreationDate_Ranking = 2018-03-26 00:00:00 +0000 kMDItemContentModificationDate = 2019-11-11 20:35:24 +0000 kMDItemContentType = "dyn.ah62d4rv4ge80g55eqy01s55wrr31a2pdqy" kMDItemContentTypeTree = ( "dyn.ah62d4rv4ge80g55eqy01s55wrr31a2pdqy", "public.data", "public.item" ) kMDItemDateAdded = 2018-03-26 01:00:14 +0000 kMDItemDateAdded_Ranking = 2018-03-26 00:00:00 +0000 kMDItemDisplayName = "Project.code-workspace" kMDItemFSContentChangeDate = 2019-11-11 20:35:24 +0000 kMDItemFSCreationDate = 2018-03-26 01:00:14 +0000 kMDItemFSCreatorCode = "" kMDItemFSFinderFlags = 0 kMDItemFSHasCustomIcon = (null) kMDItemFSInvisible = 0 kMDItemFSIsExtensionHidden = 0 kMDItemFSIsStationery = (null) kMDItemFSLabel = 0 kMDItemFSName = "Project.code-workspace" kMDItemFSNodeCount = (null) kMDItemFSOwnerGroupID = 20 kMDItemFSOwnerUserID = 501 kMDItemFSSize = 377 kMDItemFSTypeCode = "" kMDItemInterestingDate_Ranking = 2020-02-15 00:00:00 +0000 kMDItemKind = "Visual Studio Code - Insiders document" kMDItemLastUsedDate = 2020-02-15 18:27:26 +0000 kMDItemLastUsedDate_Ranking = 2020-02-15 00:00:00 +0000 kMDItemLogicalSize = 377 kMDItemPhysicalSize = 4096 kMDItemUseCount = 598 kMDItemUsedDates = ( "2020-02-15 05:00:00 +0000" ) And the output for one that doesn't appear in the results is: kMDItemFSContentChangeDate = (null) kMDItemFSCreationDate = (null) kMDItemFSCreatorCode = "" kMDItemFSFinderFlags = (null) kMDItemFSHasCustomIcon = (null) kMDItemFSInvisible = 0 kMDItemFSIsExtensionHidden = (null) kMDItemFSIsStationery = (null) kMDItemFSLabel = (null) kMDItemFSName = (null) kMDItemFSNodeCount = (null) kMDItemFSOwnerGroupID = (null) kMDItemFSOwnerUserID = (null) kMDItemFSSize = (null) kMDItemFSTypeCode = "" Clearly something is wrong here! But is there anything that I, or Alfred, can do about this? The latter file appears file in a normal file search, in both Spotlight and Alfred. But it doesn't appear in the File Filter, since I'm filtering for a something type of file, and apparently, even though this file has the correct file extension (.code-workspace), it doesn't have the correct metadata. The weird thing is, after 10 minutes, the metadata gets populated for the file. But of course, I'd like to be able to create a file, and access it in Alfred, immediately.
  3. I think since updating to Alfred 4.0.7, which came out on Dec. 17, I've got some apps that no longer appear. Sometimes, I'll have apps outside of the /Applications dir, so I create a shortcut to them in the /Applications dir. But those shortcuts no longer appear in Alfred. Also, one specific app, JDiskReport.app, no longer appears in Alfred, even though it's in my Applications dir. These missing items appear fine in Spotlight.
  4. That didn't help for me. Got any other suggestions?
  5. Perhaps similar to this issue. If I type too fast, then extra results that should not match, still appear, for a File Filter. If I type `term`, then one particular item appears. But I have a File Filter for `ter` which searches within a specific folder, yet the item from the first search still appears if I type too fast. In the GIF, you can see me type fast first, then slow.
  6. If I'm typing too fast during a File Filter search, and I type a space, then Alfred can't find any results. Only when I start typing letters again will it find results. I don't have a problem if I type too slowly. Animated GIF attached.
  7. It turns out that the problem was I needed to uncheck "Source files" on the File Search > Search page.
  8. Thanks, I tried it earlier, but the path I used must have had some messed up characters. It works now.
  9. Is it possible to open any file on my Mac, by pasting the full path to a file into Alfred? The closest I know of is the `open` command, which I think only searches the specified folders in Alfred, so it doesn't actually allow for "any" path?
  10. Running "reload" seems to usually fix it. I'll report back if things are still not working well. Thanks!
  11. Is there any problems with having the Alfred env vars exist in my shell? Or it just leads to possible "confusion", such as if my script is trying to read an Alfred env var, then the value would possibly be incorrect? The reason I open apps like Terminal via a workflow using system commands (os.system in Python) rather than Alfred's method, is because I usually also need to pass args to the commands. And depending on the keywords used, a different app would be opened, etc.
  12. I'm not sure how the Alfred env vars ended up in my Bash env. I have a workflow called "Finder" on my Mac, which contains several File Filters that I use to look for specific file types in different folders. That's the one whose Alfred env vars appear in my Bash, such as "alfred_workflow_uid" and "alfred_workflow_name". "alfred_workflow_bundleid" is not set though. I don't know where these vars are being set. I looked in the usual places like ~/.bash_profile, ~/.bashrc, etc. but couldn't find them. --- Upon further inspection, I think I know why the Alfred env vars appear in Bash. What happens is that I have an Alfred workflow that opens iTerm, and therefore when I open iTerm with this workflow, the env vars are set. If I open iTerm through the Dock, then no Alfred env vars are set. So it seems to simply be working normally.
  13. Thanks, but this variable also exists when I run the script outside of Alfred. Looking at `env` in Bash, I actually have a ton of Alfred variables already set there. I found a few `alfred_` keys that exist only in the workflow though, so I'll use one of those other ones.
  14. Is there an environment variable that Alfred sets, that indicates that it's running a script in a workflow? I'd like to use this variable to set the script's environment to "production" when it's set, and to "development" when not.
  15. Thanks for the example workflow. I suppose it is not possible to have live updating results when using the File Filter this way? For instance, normally if you change your input keyword, then the results would change to use your new keyword. But with this workflow, you only get results once you submit your keyword to the File Filter.
  16. I have two File Filters that are similar. They each essentially return the same file types from the same folder, except for a few file type differences. One keyword is "p" and the other is "pr". If I type "pr test" then I have some results appear, as expected. if I delete the "r" from the keyword so that it appears as "p test", then no results appear. I have to modify the search, such as by simply adding a space somewhere, before results appear correctly for "p test".
  17. The file filter placeholder shows if I type the keyword, as expected, but then no results are returned when I type the query, correct. I have the same problem even after hiding and re-showing Alfred.
  18. I have a File Filter to look for specific file types in a specific folder. If I create a new file in this folder that matches these requirements, then use the File Filter keyword to look for this new file, then the new file does not appear. I have to restart Alfred before the new file appears. Yet, I can find the file just fine immediately in Spotlight and Alfred's normal file search. What can I do so that I don't have to restart Alfred whenever I add a new file?
  19. Okay thanks. I didn't know that worked. It definitely isn't intuitive, unless shown for the first time. The "keyword" field in "file filter" should probably be greyed out if it's receiving its input from elsewhere.
  20. I'm not sure how this is supposed to be done then? I have attached screenshots showing what I have. I created a test workflow, with one Keyword leading to one File Filter. If I type "test asdf" in Alfred and hit Enter, it leads to "asdf" as the only keyword in Alfred, with no result.
  21. Thanks for the response. However, doesn't the File Filter need a keyword though? How do I create a keyword, which leads to a variable, which leads to a File Filter, if the File Filter itself needs a keyword and a search query, which will then filter the contents of the folder with the query?
  22. I have several keywords for file filters, that lead to several outputs. The file filters are all actually the same; it's just the keywords and outputs that are different. Is it possible at all to share the same file filter among several keywords and outputs, so I don't duplicate the filter? Since if I ever need to change it, then I have to modify it for every occurrence, rather than just a single one, which would make it much easier.
  23. Is it possible to prioritize one file extension over another in the results, without hiding results for the secondary file extension completely? And without creating separate searches for the two extensions?
×
×
  • Create New...