dsh-at-file-everything

LIMITATIONS

Known limitations

- **Windows only**, and only as good as the Everything index. Files excluded from indexing are invisible here too — to `find_files` as well as to `@`. - **Everything must be running.** If the service is down the plugin logs that specific cause, completion answers nothing, and `find_files` raises an error naming the cause and pointing at `glob`. The bundled `es.exe` supplies the *client*, not the service, so it cannot help here. - **The bundled client is pinned.** It is chosen for Everything 1.4 latency (see `bin/README.md`). On a future Everything whose `count:` filter is cheap, a newer client would be the better pin; a user-supplied `es.exe` on `PATH` or in `esCommand` always takes precedence, so this only affects machines relying on the fallback. - **Filename-scoped search.** Typing a directory path with `/` lists that directory, but a bare query will not match deep path fragments that no file name contains — the upstream substring path match was traded for the ~30× latency of the index path. `find_files` searches names only, so the same applies. - **`find_files` pages, it does not stream.** One call returns at most 500 entries; past that the model must narrow the query or page by raising `limit`. The result says so. - **One `es.exe` process per query.** Each query is a fresh process (~70–80 ms warm). Cancellation kills it. - **First query after Everything's index is cold** can take ~1 s as the service pages the index in; `timeoutMs` covers that wait, `deadlineMs` covers the process.