---

8.13.3 Feedback differs between buffers ¶

Different applications deliberately announce different information. Compare the same kind of item and the same action before treating that difference as a fault. An explicit request for detail can also speak more than automatic feedback without ignoring the saved automatic policy.

If the problem is too much speech, first identify what was added. Automatic application content belongs to its focused speech settings. Training adds explanations across buffers; inspect its current state in C-e H r before changing it. Extra labels can come from Presentation Options or rules. Speech that arrives independently may be a notification; use notification routing to understand that stream rather than treating it as part of the line you are reading.

1. In the affected buffer, use C-e S to inspect its focused settings, or general buffer settings when no focused integration menu is available. Read the current values before toggling anything.
2. Use C-e H d to compare captured-buffer values with global defaults and saved values known to Customize. Return from the snapshot before choosing a different buffer and opening a fresh comparison.
3. Explain the affected item with C-e E. Inspect matching buffer or session rules, Presentation Options, Voice Lock and explicit face presentation. These contributions need not be the same in another buffer.
4. Change only the setting or rule that explains the difference. Return to the original item, repeat the action, and check an unaffected buffer too. Restore the earlier value if the change does not address the symptom.

Integration speech settings explains the different saving boundaries. Use the application’s own chapter for automatic-speech limits and privacy; do not assume the same key or background setting has the same effect in EAT, Shell/comint, Notmuch and Agent Shell.