On 25 Mar 2014, at 6:33, Lucas Garron wrote:
I've been using Quicksilver for a long while, so it almost seems
embarrassing to ask, but maybe I'm missing something or someone has
seen
this before:
Should the indexing/rescan system be remotely reliable?
I’m equally embarrassed to say I’m not sure. I destroy and recreate
my catalog so often when testing different things, I’d probably never
notice.
Most of my catalog entries are set to rescan "Every 10 minutes".
Maybe you know, but for everyone else’s benefit: It doesn’t
literally rescan everything on a schedule. It just asks each entry if
it’s still valid since the last scan. Only if the entry says “no”
will a rescan of that entry actually take place.
However, when I add something to the entry (e.g. a folder/file in an
indexed folder), it can take a long time for the entry to show up in
the
index. In fact, I'm not sure if things show up at all, because
sometimes I
get impatient after a long while and force a rescan.
I know if you change a file, the parent folder’s timestamp is changed
too, but I’m not sure about the folders above that. So the “File &
Folder Scanner” might not pick up changes two or more levels deep
because the answer to the “Are you still valid?” question will be
“yes”, so no rescan.
(There are a small number of File & Folder presets that update in
real-time as soon as a change happens, but that’s rare.)
I think it happens with multiple types of catalog entries, but my
primary
annoyance is folders.
They all have their own criteria for determining if a rescan is
required, so it could be that there are different bugs in different
places.
Running "Force Catalog Rescan" (from Internal Commands) works,
although
that takes a few seconds, of course. "Catalog Rescan" and Cmd-R don't
work.
I thought those *did* force a rescan, but probably not if there’s a
separate command for it. You can see that I’m an expert in this area.
;-)
I'm not sure if rescans happen with any frequency, but I keep running
into the issue. The long debug cycle (at least, when things should be
working correctly) makes me reluctant to figure out exactly what's
going on.
All I can say is to make a test folder and add it to the catalog and try
different things periodically. Or, since you can probably understand
[the code][1], maybe you just want to start there and look for obvious
flaws.
--
Rob McBroom
http://www.skurfer.com/
[1]:
https://github.com/quicksilver/Quicksilver/blob/master/Quicksilver/PlugIns-Main/QSCorePlugIn/Code/QSFileSystemObjectSource.m#L393
--
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/d/optout.
