You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QSRequirements can refer to bundles or paths. I think we should be able to do something similar for relatedBundles. That is, I’d like to add support for a relatedPaths key in a plug-in’s Info.plist. The effect would be that if one of the paths exists, the plug-in will show up on the recommended list (and in the first-run spinning cube).
Why? I recently removed com.apple.Terminal from the Terminal plug-in’s relatedBundles because it doesn’t need to be recommended to all users, but surely we should be able to recommend it to some. So I was thinking we could just check for something only Terminal users are likely to have, such as /usr/local/bin. Remote Hosts could benefit from something similar, and I’m sure there are others.
The text was updated successfully, but these errors were encountered:
QSRequirements
can refer to bundles or paths. I think we should be able to do something similar forrelatedBundles
. That is, I’d like to add support for arelatedPaths
key in a plug-in’sInfo.plist
. The effect would be that if one of the paths exists, the plug-in will show up on the recommended list (and in the first-run spinning cube).Why? I recently removed
com.apple.Terminal
from the Terminal plug-in’srelatedBundles
because it doesn’t need to be recommended to all users, but surely we should be able to recommend it to some. So I was thinking we could just check for something only Terminal users are likely to have, such as/usr/local/bin
. Remote Hosts could benefit from something similar, and I’m sure there are others.The text was updated successfully, but these errors were encountered: