| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| SHA256SUMS.txt | 2026-09-01 | 85 Bytes | |
| ShortGeekSetup.exe | 2026-09-01 | 87.4 MB | |
| README.md | 2026-09-01 | 1.3 kB | |
| ShortGeek 1.0.2 source code.tar.gz | 2026-09-01 | 956.1 kB | |
| ShortGeek 1.0.2 source code.zip | 2026-09-01 | 977.2 kB | |
| Totals: 5 Items | 89.4 MB | 0 | |
Fixes the app failing to start with "Unable to configure formatter 'default'".
If 1.0.1 gave you a box saying ShortGeek could not start, with a traceback ending in that line, this is the fix. Nothing was wrong with your machine.
What was wrong
A windowed application has no console, so it starts with nowhere to write at all. The web server inside ShortGeek tried to ask that nowhere whether it was a terminal, so it could decide whether to colour its log output, and fell over on the first line. The server never started and the window had nothing to show.
It now writes to a log file in your own profile instead, and the server does not configure logging at all.
Why the build did not catch it
1.0.1 added a check that starts the packaged app and asks it for a page. That check redirected the app's output to files so the build log could show it, and handing the app somewhere to write is precisely what hid the fault.
The check now runs the app twice: once normally, and once with its output taken away, which is the shape you actually get. Nothing is redirected. If it fails, the build prints the app's own log files, which are the same ones you would attach to an issue.
Downloads below: ShortGeekSetup.exe. SHA256SUMS.txt lists its hash.
