Everything search: no effect

[Ovg]

2Flint

Try 1.4.0.713 - I use this version and for me it working fine

[Flint]

Ovg
Installed it, no luck, still the same problem.

[Ovg]

2Flint
Sorry, I have no more ideas

[EricB]

2Flint

Are you using a named instance for Everything? TC cannot find those, see thread
http://www.ghisler.ch/board/viewtopic.php?t=44441&postdays=0&postorder=asc&start=0

Regards, EricB

[Flint]

EricB
I don't think I do. The service process is running with command line
"C:\Program Files\Everything\Everything.exe" -svc
and the UI instance is:
"C:\Program Files\Everything\Everything.exe" -startup
(checked via Process Explorer). They both don't have the -instance argument.

[EricB]

Flint
I had also this problem and it was the Everything= key in wincmd.ini that I misplaced under the wrong section. It should be in [Configuration]. If you have the key there, maybe the path is the problem (it might need some quotes here and there due to the space in the path name).

Regards, EricB

[Flint]

EricB
I thought this key was only needed when Everything is NOT running, so that TC could start it. In my case it is already running, so no, I do not have this key in my INI file at all.

Just in case, I tried starting TC with fresh INI file with the following contents:

Code: Select all

[Configuration]
Everything="C:\Program Files\Everything\Everything.exe" -startup

It did not help, TC still could find nothing.

[ghisler(Author)]

Sorry, I have no idea why it doesn't work for you. TC uses the official Everything API and includes the right dlls. TC looks for the running everything window, and if it isn't there, tries to start Everything, and otherwise show an error.

[Flint]

ghisler(Author)
I investigated a little and found that an Everything option is what breaks TC:

Everything Options -> General -> Search -> "Match path when a search term contains a path separator"

When this checkbox is turned OFF (like on my computer), TC search fails. When I turned this option ON, TC started to get some results.

[Horst.Epp]

ghisler(Author)
I investigated a little and found that an Everything option is what breaks TC:

Everything Options -> General -> Search -> "Match path when a search term contains a path separator"

When this checkbox is turned OFF (like on my computer), TC search fails. When I turned this option ON, TC started to get some results.

It doesn't break Everything !
Searches from TC are working fine with this option set.
I use this options since beginning of Everything years ago
and also now with TC of course.
Using Everything syntax and its options means you understand Everything
You have just to adjust your searches according to the options you set.

[Flint]

I use this options since beginning of Everything years ago
and also now with TC of course.

It's ABSENCE of this option that breaks the search, not its presence.

Or do you mean I can turn it back on and continue to use Everything without problems? Well, of course I know I can, but it's not the point. Point is that TC should not behave like that, or at least (if the problem cannot be solved) it must be documented and, if possible, user should be warned by TC about this incompatibility.

[Horst.Epp]

I use this options since beginning of Everything years ago
and also now with TC of course.

It's ABSENCE of this option that breaks the search, not its presence.

Or do you mean I can turn it back on and continue to use Everything without problems? Well, of course I know I can, but it's not the point. Point is that TC should not behave like that, or at least (if the problem cannot be solved) it must be documented and, if possible, user should be warned by TC about this incompatibility.

Its better to have the option set but it also works with its absence !
If this option is absent searching for something containing a path requires you to search like the following example in TC:
ev:path:\temp\test
This searches for any dir temp with a sub-dir test
There is nothing to warn or document in TC because thats how Everything works.
Using Everything without any knowledge about its options and syntax is useless.

[Lefteous]

I can confirm Flint's report.

[Flint]

Horst.Epp
I disagree with your reasoning. The "Everything" checkbox in TC does not suggest that whole request syntax immediately changes. Therefore, most users will expect TC to continue searching for files exactly the same when using Everything as it did without (only faster). If somebody wants extended Everything-specific features, there is an addition in the form of ev syntax, but it is not a requirement. Not to mention that even if it were a requirement it should have always been a requirement, not something that suddenly jumps out at you when you switch one not very significant Everything option.

So I still think this behavior must be either fixed or, if impossible, documented with warning signs.

[ZoSTeR]

Since TC always populates the "Search in" field I was about to suggest to start Everything with "-startup -matchpath" by default but it seem that this parameter is ignored.
Bug in Everything or do I misinterpret this setting?

Edit:
The parameter -matchpath only gets applied if you pass a search (-s).

@ghisler: TC should always set "Everything_SetMatchPath" in the query since it always passes a path even if the "Search in" field is empty.