8.13.2 A setting disappeared after restarting ¶
First establish whether the change was ever meant to survive restarting.
A retained draft, session rule or buffer rule does not. Activating a palette
for a session is also separate from choosing it at startup.
- Identify the resource you changed: a named voice, rule, profile, speech
control or host setting. Reopen its own editor or manager and check its
saved state. Do not assume it is absent merely because it is not active.
- For a saved palette, inspect the selected startup profile. Use Use at
Startup only when you intend to change that profile’s palette. Applying
a Presentation Profile also retains its selection; a profile does not
contain speech rate, engine policy, notification output or temporary rules.
- For an individual control, check exactly what that menu’s Save records.
The changed-settings snapshot can compare values known to Customize, but
it is not a complete inspection of voice, rule or host-side files.
- If the saved value exists but is not effective, check a mode policy or
buffer override before saving again. For host-side settings, use the
owning editor’s application or restart procedure, not a voice-palette Save.
Customize saves need a normal initialisation destination. If Emacsvox reports
"Settings were not saved" because normal initialisation was skipped, possibly
with the -q startup option, restart with your usual configuration and save
again. A temporary change in that session is not a successful saved default.
For spelling, the tone editor’s W saves the tone itself; use S in its
parent Spelling feedback menu to save voice, tone and earcon enablement too.
Use Choose what persists to select the intended action. Check the result in
the current session first. A later restart tests startup selection; finish
or deliberately save needed work beforehand because retained drafts will end.
Do not use a restart as the first way to investigate an unfinished draft.