Docs: where the portable marker goes on macOS, AppImage and Flatpak; keep a portable copy where only you can write (#1366)

This commit is contained in:
Marco Arnulfo
2026-10-16 15:27:55 +07:00
committed by bflatastic
parent d21040d746
commit 830dea80e0
3 changed files with 22 additions and 7 deletions
+3 -1
View File
@@ -12,7 +12,9 @@ logs, recovery and user libraries then use that root, without importing the lega
An unset override preserves the usual platform paths and legacy migration; an explicitly empty override
disables those paths. `VECTORCRAFT_NO_PREFS` continues to disable preference reads and writes.
Without the override, a `portable.txt` or `VectorCraft.portable` file beside the executable (as in the
Windows portable zip) puts that root in `VectorCraftData` next to the executable.
Windows portable zip) puts that root in `VectorCraftData` next to the executable; on macOS the marker
and the folder sit next to `VectorCraft.app`, for an AppImage next to the `.AppImage` file, and a
Flatpak install has neither. `VECTORCRAFT_NO_PREFS` never looks for the marker or creates the folder.
**Only requests are read.** Every line must be a JSON object with a string `method` (`id` and `params`
are optional; blank lines are skipped). Anything else gets one error reply