LogAce separates durable preferences and source state from rebuildable working data. That keeps profiles, bookmarks, layouts, histories, and sessions available without treating downloaded snapshots or live spools as permanent records.
A sidecar stores source-specific analysis and presentation choices. It does not copy the source contents.
The selected profile ID, text encoding, and any Ad Hoc profile definition are retained so the source can be interpreted the same way next time.
The current physical anchor line and bookmark collection are restored against the source.
Column visibility, widths, wrapping, maximum cell height, and derived virtual columns are stored per profile.
The expression text and its enabled state persist, allowing a saved predicate to return active or intentionally disabled.
state ~/Library/Application Support/LogAce cache ~/Library/Caches/LogAce
state ${XDG_STATE_HOME:-~/.local/state}/logace cache ${XDG_CACHE_HOME:-~/.cache}/logace
state %LOCALAPPDATA%\LogAce\State cache %LOCALAPPDATA%\LogAce\Cache
preferences.json, recent history.json, expression and query histories, user profiles.json, sessions.json, saved SSH connections, and Query Tab definitions live under the state directory.
Hashed local-file state and source descriptors for remote, cloud, device, listener, archive, merge, and query workflows use dedicated state subdirectories.
Archive and gzip extraction, remote snapshots, live-source spools, merged timelines, stdin, and materialized Query Tab results use the cache directory.
F1 → About reports the resolved state and cache directories, preferences, histories, profiles, GeoIP databases, and individual source spool locations for the running build.
File → Save Session records the eligible tabs, their order, the active tab, and expression-filter overrides. File → Open Session reopens that set additively beside tabs that are already open.