mindfork 0.18.1 — where everything is
mindfork 0.18.1 is out. It is a small release with one addition: the app now says where its files are.
Three folders, one look
Until now the interface named no folder at all. mindfork stats printed the
data folder, and the logs' path turned up only in an error message. F1 →
About now ends with a Locations group:
- Program — the folder the binary is in.
- Data — the data folder, and in its label how it was chosen: portable
(beside the binary), standard folder (your user folder) or custom folder
(one named in
defaults.json). - Logs — where the log files are, the first thing a bug report asks for.
The paths are full, never ~, so a row can be pasted into a file manager or a
shell as it is. A path too wide to sit beside its label goes on a line of its
own under it, wrapped but never cut short.
Which folder the data went to depends on the route: the portable archives, the
one-line script and cargo install keep it beside the binary; the Linux
packages, Homebrew and Scoop use your user folder; the Windows installer asks.
On a rented GPU box the data row answers the question that matters there —
whether the data is on the volume that outlives a stop, or on a disk that does
not.
mindfork demo shows a made-up set of folders instead of yours, so a
screenshot of it carries none of your paths.
Your data
Nothing in the data's format changes, and no step runs at the start.
The full list is in the
changelog;
downloads are on the
releases page, and
cargo install mindfork builds the same version from
crates.io.