Just A rant ! Everything and Seamonkey poorly programmed.

In message , Char Jackson
writes:
On Thu, 18 Apr 2019 16:12:03 -0400, Paul wrote:
[]
This becomes a "loop", if you inadvertently have the
database itself in a "visible" place that Everything.exe
can index. Everything does (3), the Journal does (1),
and the thing goes around in a merry circle.

I don't think that's an actual issue, although it sounds good in theory.

I occasionally find Everything using 25% of my CPU (most of one core and
a bit of another - four core machine), even when it - and the computer -
aren't doing anything out of the ordinary. One other poster in this
'group has also experienced high CPU usage, though in his case I think
he had two Everythings running for some reason. Paul and others
postulated it might be some such looping behaviour; I'm afraid it
doesn't happen often enough (and can be got rid of by stopping [from the
tray, not Task Manager] and restarting Everything) that I have more or
less abandoned investigating it.

I'd bet that each of us who use Everything are able to type "everything"
into its interface and see, among the results, its index file. There's
never been any noticeable looping behavior, AFAIK.

Is that Everything.db? If so, yes, I can see it. (Timestamped just under
12 hours ago, which surprises me: I thought it'd be more recent. So
maybe I'm _not_ seeing its index.)

Its author probably took care of that behavior a very long time ago, in
one of the earliest versions.

You'd have thought so. Certainly the busy behaviour I occasionally see
seems to be rare - until the other poster posted (and he had SeaMonkey
also playing up, so may not have had a true Everything problem), I
seemed to be the only one here experiencing it.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Going to church doesn't make you a Christian anymore than going to a garage
makes you a car." - Laurence J. Peter

On Tue, 30 Apr 2019 01:21:47 +0100, "J. P. Gilliver (John)"
wrote:

In message , Char Jackson
writes:
On Thu, 18 Apr 2019 16:12:03 -0400, Paul wrote:
[]
This becomes a "loop", if you inadvertently have the
database itself in a "visible" place that Everything.exe
can index. Everything does (3), the Journal does (1),
and the thing goes around in a merry circle.

I don't think that's an actual issue, although it sounds good in theory.

I occasionally find Everything using 25% of my CPU (most of one core and
a bit of another - four core machine), even when it - and the computer -
aren't doing anything out of the ordinary. One other poster in this
'group has also experienced high CPU usage, though in his case I think
he had two Everythings running for some reason. Paul and others
postulated it might be some such looping behaviour; I'm afraid it
doesn't happen often enough (and can be got rid of by stopping [from the
tray, not Task Manager] and restarting Everything) that I have more or
less abandoned investigating it.

I'd bet that each of us who use Everything are able to type "everything"
into its interface and see, among the results, its index file. There's
never been any noticeable looping behavior, AFAIK.

Is that Everything.db? If so, yes, I can see it. (Timestamped just under
12 hours ago, which surprises me: I thought it'd be more recent. So
maybe I'm _not_ seeing its index.)

I just checked and mine is a bit over 9 hours old.

Its author probably took care of that behavior a very long time ago, in
one of the earliest versions.

You'd have thought so. Certainly the busy behaviour I occasionally see
seems to be rare - until the other poster posted (and he had SeaMonkey
also playing up, so may not have had a true Everything problem), I
seemed to be the only one here experiencing it.

--

Char Jackson