Make vim editing mode a persistent user setting (enabled by default)

[DanyaIT]

Request: Make vim editing mode a persistent user setting (enabled by default)

Repo: ccch1mneyyy/dsh-TUI
Package: @deepseek-harness-tui/dsh-tui v0.11.1
Type: Feature request
Priority: Low
Labels: enhancement, settings

---

Problem

The prompt input supports a vim editing mode toggled with the /vim command, but it is off by default and session-scoped — the internal comment notes "the mode is session-scoped (not persisted)".

For vim users this means:

• Typing /vim at the start of every new session, and
• Re-toggling it after any action that resets the session state.

There is currently no way to make vim mode the default across sessions.

Current behavior

lib/types/components/PromptInput.js (~line 462):

const [vimEnabled, setVimEnabled] = React.useState(false);

• Defaults to false.
• Toggling /vim only affects the current session; the preference is not saved.

Proposed behavior

Add a persisted user setting (e.g. vimMode, or nested as prompt.vimMode) that controls whether vim editing mode is on by default:

1. The initial value of vimEnabled is read from the setting:

   const [vimEnabled, setVimEnabled] = React.useState(settings.vimMode ?? false);

2. The /vim toggle writes the choice back to the setting, so the preference persists across sessions.

3. Non-vim users are unaffected — they keep their existing default (false).

Why a setting rather than a hardcoded default? A hardcoded true would (a) change the default for everyone, (b) get overwritten on the next dependency reinstall, and (c) force non-vim users to opt out on every session. A setting lets each user choose their own preference.

Acceptance criteria

• A persisted user setting controls the vim-mode default (true/false).
• The /vim toggle updates the setting so the choice survives restarts.
• New sessions start with the user's saved preference.
• Non-vim users see no change unless they opt in.
• The setting is surfaced/discoverable in the Settings UI and documented.

Files / areas involved

• lib/types/components/PromptInput.js — seed vimEnabled from the setting; persist on toggle.
• Settings/config layer (wherever settings is defined and persisted).
• Settings UI — expose the toggle.
• Docs — note the new setting.

Notes / open questions

• Draft-snapshot interaction: setVimEnabled(snapshot.vimEnabled) restores the vim mode from the draft cache. Should a restored draft override the user setting, or should the setting win for the session? Worth deciding explicitly.
• vimEnabledRef is re-synced from vimEnabled every render, so it follows the setting automatically — no separate change needed there.