The problem
After some time, closed issues build up in the default view mode. The v view-mode cycle (All -> Active -> Ready) hides them, but it resets to All on every launch, so I have to press v every session. There's no config option for the startup default.
Desired behavior
Add a config key that controls the initial view mode at startup:
- Key
view.mode (string), accepted values all | active | ready, default all (preserves current behavior)
- On launch,
App.viewMode is initialized from this key instead of always defaulting to ViewModeAll
- The in-app
v / V cycle keeps working and can still move away from the configured default for the current session
- An unknown/invalid value falls back to
all (optionally with a warning)
Acceptance criteria
Out of scope
- Persisting a
v-chosen mode back to config (making the current setting sticky across launches). This request is just for a read-only startup default
The problem
After some time, closed issues build up in the default view mode. The
vview-mode cycle (All -> Active -> Ready) hides them, but it resets toAllon every launch, so I have to pressvevery session. There's no config option for the startup default.Desired behavior
Add a config key that controls the initial view mode at startup:
view.mode(string), accepted valuesall | active | ready, defaultall(preserves current behavior)App.viewModeis initialized from this key instead of always defaulting toViewModeAllv / Vcycle keeps working and can still move away from the configured default for the current sessionall(optionally with a warning)Acceptance criteria
view.mode: activein~/.abacus/config.yaml, launchingabacusstarts in the Active view closed/blocked/deferred hidden) with novpressview.mode: ready, it starts in the Ready viewall, behavior is unchanged from currentallv/Vstill cycle view modes at runtime as beforeOut of scope
v-chosen mode back to config (making the current setting sticky across launches). This request is just for a read-only startup default