ES not Compatible with Everything 1.4.0 ?

[therube]

I'm guessing ...

ES (Everything Command-line Interface) is not Compatible with Everything 1.4.0's Service?

Actually, not sure?
Not sure what's going on?

ES NCMAIN.EXE, works as expected
ES -?, works as expected
but ES alone (which should list all files) seems to want to start doing something, but then nothing ?
(I don't recall ES alone just doing nothing, hanging [needing a Ctrl-C to quite], but I could be wrong?)

Or maybe its the database?

ES says "Search the database".
How does it know where the database is?
Is it searching "the database" (like everything.db) or is it reading the MFT directly?

Win XP

[therube]

Win 7, & don't seem to have the issue here?
Slight delay after hitting ES+c/r, but otherwise, fine.

[void]

Thanks for the bug report.

ES will only connect to the unnamed instance of Everything.
The unnamed instance of Everything must be running.

Adding instance support to ES is on my TODO list.

Depending on the number of results you may experience a slight delay.

ES (Everything Command-line Interface) is not Compatible with Everything 1.4.0's Service?

How does it know where the database is?

ES basically connects to the Everything tray icon window via IPC.
Everything must be running for ES to function.

but ES alone (which should list all files) seems to want to start doing something, but then nothing ?

It would be trying to send all results over IPC. It may take a couple minutes.

[void]

There's another issue here, Everything can crash after the IPC request.

I'll have a fix soon.