Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spotlight results #778

Merged
merged 1 commit into from Apr 16, 2012
Merged

Spotlight results #778

merged 1 commit into from Apr 16, 2012

Conversation

skurfer
Copy link
Member

@skurfer skurfer commented Mar 28, 2012

As discussed on the list, I’ve created a new category to simplify a common Spotlight task: give me the current results and go away. I see a need for this in at least three plug-ins off the top of my head. No one objected, so here it is. :-)

A brief description can be found in the header.

@pjrobertson
Copy link
Member

pjrobertson commented Apr 16, 2012

I played with this thinking it could be used for a new Mail module. Unfortunately the results returned don't contain any info on the mailbox, so I don't think it can be used.

None-the-less, this is handy :)

pjrobertson added a commit that referenced this pull request Apr 16, 2012
@pjrobertson pjrobertson merged commit b5583b3 into quicksilver:master Apr 16, 2012
@skurfer
Copy link
Member Author

skurfer commented Apr 16, 2012

I played with this thinking it could be used for a new Mail module. Unfortunately the results returned don't contain any info on the mailbox, so I don't think it can be used.

What do we need about the Mailbox other than its name? I did a stand-alone command line tool that used this category to dig through the mail folder structure (just as a proof of concept), and it seemed to work well.

@pjrobertson
Copy link
Member

pjrobertson commented Apr 16, 2012

What do we need about the Mailbox other than its name?

Nothing really, but how do you get the mailbox name? You could possible try
and sniff it out of the 'path', but I don't know how reliable that is.
Great news if you've got something working though, I know little about
mdfind so I probably overlooked something.

On 16 April 2012 14:13, Rob McBroom <
reply@reply.github.com

wrote:

I played with this thinking it could be used for a new Mail module.
Unfortunately the results returned don't contain any info on the mailbox,
so I don't think it can be used.

What do we need about the Mailbox other than its name? I did a stand-alone
command line tool that used this category to dig through the mail folder
structure (just as a proof of concept), and it seemed to work well.


Reply to this email directly or view it on GitHub:
#778 (comment)

@skurfer
Copy link
Member Author

skurfer commented Apr 16, 2012

You could possible try and sniff it out of the 'path', but I don't know how reliable that is.

That’s what I was thinking. In fact, the small example I cooked up uses plain old NSFileManager stuff for mailboxes. It only resorts to Spotlight for getting messages, since that’s where the directory structure gets tricky.

Thanks for merging, by the way. Once #804 is in, we can release an updated Spotlight plug-in.

@lovequicksilver
Copy link

lovequicksilver commented May 9, 2012

Thanks, this is useful!

Using this in the ß68 prerelease. When Using 'Spotlight Filenames of Contents…' or 'Spotlight Contents…', QS returns the magnifying glass 'Searching' message only. Pressing ↓ or ↑ will then show a search result in pane 1. Occasionally I then see the results in the list, usually I see just the first result found or the 'Searching' icon.

@skurfer
Copy link
Member Author

skurfer commented May 10, 2012

I wouldn’t expect the Spotlight plug-in to work any better that it did before. This just lays the groundwork so I can fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants