16.5 Work in an application ¶
- Open the right file: check the buffer and full pathname before editing.
- Keep the original and work on a copy: distinguish current buffer text
from the last saved file, and check where later saves will go.
- Find a file and hear its details: browse names, inspect size or date,
and return without deleting or moving files.
- Write a note I can reopen later: create a real Org file rather than
leaving the text in a disposable buffer.
- Review a document and correct a word: reveal headings and body text,
inspect a small edit, and save the intended version.
- Read a web page: enter an address and identify the rendered browser
buffer before using navigation keys.
- Find information within a page: use its HTML structure or search the
loaded text, without submitting a new web search.
- Follow a link and get back: distinguish browser history,
separate buffers and saved website bookmarks.
- Limit the mail details spoken automatically: choose fields, bounds, and
completion feedback. Explicit full-detail reading bypasses automatic bounds.
- Hear a terminal’s completion candidates: keep terminal-side completion
separate from Emacs completion and inspect retained candidates when needed.
- Review terminal output without sending input: use EAT’s frozen review for
a retained screen. Term review follows a different, live-buffer model.
- Enter a terminal password safely: use EAT’s protected input operation and
understand why ordinary no-echo input is not the same boundary.
- Read the last completed agent response in full: explicitly inspect the
successful response rather than changing the automatic speech policy.
- Copy code from an agent response: navigate to its source block and use
the logical copy operation rather than selecting renderer padding.
For other applications, begin with Applications and Integrations and the
active buffer’s mode Help.