Prevent Spotlight from indexing terminal-notifier.app #238
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit places
terminal-notifier.app
in amac.noindex
folder so that Spotlight does not index the app (Spotlight does not index folders ending with.noindex
).If you happen to have a few npm packages depending on node-notifier installed, you’ll encounter quite a few
terminal-notifier.app
results when searching for “Terminal” in Spotlight (or in any other app launcher that uses Spotlight’s index). Since there’s no point in openingterminal-notifier.app
by itself and it just clutters Spotlight’s results, I’d suggest removing it from the index.Side note: Why not
.metadata_never_index
?The above-linked Stack Overflow answer also mentions
.metadata_never_index
as a way to prevent Spotlight from indexing a folder. However, as noted by Nate in the comments and mentioned in OS X Incident Response: Scripting and Analysis, it only seems to work at the root of a volume.