Not really, no. If the Spotlight source feeding QS's catalogue reports that nothing exists at /Volumes/SomeNetworkDrive/* anymore, QS will remove all catalogue entries for files on SomeNetworkDrive. If later QS asks the Spotlight source for an update and this time the Spotlight source finds files matching its query on SomeNetworkDrive, those files will be added back to QS's catalogue.
To be clear, the Spotlight plugin does not allow QS to use the Spotlight database as its own catalogue. The Spotlight plugin allows QS to run a Spotlight query as a way to find files to add to its own catalogue. On Wednesday, June 26, 2013 7:40:22 PM UTC-4, David Rees wrote: > > It wouldn't help with browsing since that doesn't use the catalog, but it > would help if he used searching instead (which I pointed out). Of course he > would have to have in the catalog, but he didn't say why he didn't want it > in the catalog. That is unless we supported private catalogs :) - > https://groups.google.com/d/topic/blacktree-quicksilver/EH0b-rKs-aU/discussion > . > > > On Monday, June 3, 2013 2:19:00 PM UTC-7, Jon Stovell wrote: >> >> I'm not sure that using a Spotlight source would really help in this >> situation, David Rees. Spotlight sources are simply another way to get >> things into Quicksilver's own catalogue. When the drive is disconnected, >> Spotlight will report to Quicksilver that the resources on that drive no >> longer exist on the system, and so Quicksilver will remove them from its >> catalogue. This isn't any different in the end from what happens when QS >> scans the drive directly. >> >> Ontonator's problem isn't with trying to get a file hierarchy into his QS >> catalogue. It is with trying to handle certain sets of items in the >> catalogue in a special way. >> >> I understand why you would think of Spotlight as a solution for this, >> though. Spotlight is able to access its full index of a connected drive >> from the moment the drive is mounted without having to rebuild, whereas QS >> has to rebuild its catalogue every time the drive is connected or removed >> in order to stay up to date. The reason is that Spotlight is able to store >> an index for each drive on each drive, whereas QS has to maintain a single >> central index for everything. That difference in construction is a >> significant one when it comes to situations like network drives. >> >> On Sunday, June 2, 2013 10:26:08 PM UTC-4, David Rees wrote: >>> >>> If you are happy to search for what you want rather than navigate to it >>> maybe you could try using a Spotlight catalog? That will put the indexing >>> on Spotlight, which I think is more aggressive in keeping an indexed cache. >>> Its definitely less load on QS. >>> >>> You would need to to be sure Spotlight is indexing those network >>> volumes. I'm not sure where things are with that, but here is one >>> reference: >>> http://krypted.com/mac-os-x/enabling-spotlight-for-network-volumes/ >>> >>> d >>> >>> On Sunday, June 2, 2013 2:01:40 PM UTC-7, Ontonator wrote: >>>> >>>> I connect to my other mac through the network, and when I try to browse >>>> it with Quicksilver, it is agonisingly slow. Is there a way to maintain an >>>> index of the other computer, but not include it in the global catalogue. >>> >>> -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/groups/opt_out.
