dburr

So apparently the "new Dropbox" (the one that moves its files to ~/Library/CloudStorage) is now out of beta, and I am now being "encouraged" to upgrade to it. So I've been doing some research and apparently there have been problems of Alfred not being able to search for files in the new location, but those appear to have been solved by a recent Alfred update. Great. But what about Alfred preference syncing?  Does it work? Are there any gotchas? What actions (if any) will I need to take once I've upgraded Dropbox and it has moved everything to ~/Library/CloudStorage?

17 hours ago, luckman212 said:

@dburr as you rightly concluded, if Spotlight doesn't show the apps, Alfred isn't going to be able to either. Sounds like something's majorly hosed with your Spotlight db. I'd follow Apple TN HT201716 for getting that rebuilt, or try `sudo mdutil -Ea` from Terminal.

Thanks for the response! I was actually able to figure out how to fully rebuild Spotlight. Ended up booting into recovery mode to delete the /.Spotlight-V100 file, then I rebooted and let it run overnight, and now both Spotlight and Alfred are properly indexing things again.

OSX 10.15.1 Catalina

Alfred 4.0.6 (1124)

Alfred is no longer indexing some of my applications. It still shows the Apple apps (Photos, Music, etc.) however no third party apps are showing up. They are also not showing up in Spotlight either, so this must be a problem in general with Spotlight indexing.  I've tried Advanced -> Clear Application Cache and Advanced -> Rebuild macOS Metadata, but none of those helps. (I have let "Rebuild MacOS Metadata" run overnight.) Also when I try the "Delete .Spotlight-V100 before reindex" I get the following error: "rm: /System/Volumes/Data/.Spotlight-V100: Operation not permitted". Any ideas?

The prerelease fixed the issue for me as well!

I'm writing an Alfred workflow that requires use of an external Unix binary.  Currently I am installing this binary using Homebrew; however when I eventually start distributing my workflow, I would rather not have to force the user to set up Xcode command line tools, install Homebrew, etc.  Ideally I'd like to distribute a pre-compiled version of the binary(s) my workflow uses, along with the workflow.  Is it possible to distribute resource(s) (such as binaries, shell scripts/Applescripts, etc.) as part of the Alfred workflow bundle?  And how would one call that binary (i.e. instead of hard-coding a path, like /usr/local/bin/foo)?

There is http://www.alfredforum.com/topic/1919-dash-documentation-for-80-apis/, but it's an workflow that integrates with Dash (paid app).

Thanks, that's actually even better than what I was hoping for, since with Dash (which I hadn't heard of until now) I can search through docs for other languages/frameworks/etc. that I work with as well.

I'm an iOS (and soon MacOS) developer and would love an Alfred workflow to search the Cocoa & Cocoa touch APIs.  Has anyone written such a beast?  Thanks!

I would love a Workflow to be able to post on App.net - but I have no idea how to do it 

 

Anyone out there already have one in the works? 

I too would love a version of AlfredTweet for App.net.  If you need any alpha/beta testers let me know

In the meantime I did find Alphred, a simple post-to-app.net workflow.  Seems to work quite well.