Skip to content

1.1.1

Choose a tag to compare

View all tags
@slaFFik slaFFik released this 10 Jun 11:46
1.1.1
This tag was signed with the committer’s verified signature.
slaFFik Slava Abakumov
SSH Key Fingerprint: Aub6bEkhCINe5lCQPEtJsoUXdCloCEJVyBLGgEkneZw
Verified
Learn about vigilant mode.
d5e9955
This commit was signed with the committer’s verified signature.
slaFFik Slava Abakumov
SSH Key Fingerprint: Aub6bEkhCINe5lCQPEtJsoUXdCloCEJVyBLGgEkneZw
Verified
Learn about vigilant mode.

Quitting Solo no longer shows the misleading "Solo HTTP API not enabled — turn it on in Solo settings" message. The plugin previously inferred the API toggle from Solo's discovery file, which Solo removes on clean quit — so a closed Solo looked identical to a disabled API.

Fixed

  • The error row now also reads the real HTTP API toggle from Solo's settings database (~/.config/soloterm/solo.db), which survives quitting Solo, and names the actual remedy:
    • Solo not running — open it — the API is enabled, Solo is just closed.
    • Solo HTTP API disabled — turn it on in Solo settings — the toggle really is off.
    • Solo not running — open it and re-enable its HTTP API — both are needed (stale discovery file from a crash, API since turned off).
  • The database is opened strictly read-only, so the plugin can never create or repair files in Solo's directory; if it can't answer (missing, locked, or a future Solo renames the setting), the plugin falls back to the previous messages instead of misreporting.
Assets 2
Loading