espanso/espanso is a privacy-first text expander written in Rust. The basic idea is simple: type a trigger such as :email, and espanso replaces it with a longer snippet. The useful part is that the workflow stays local instead of sending typed content to a hosted service.
The first setup gotcha is configuration location. Espanso uses platform-specific directories, so avoid hard-coding a path in scripts that must run on macOS, Linux, and Windows. Check the active configuration directory first:
espanso path config
On Linux, a minimal match file commonly lives under ~/.config/espanso/match/. For example:
mkdir -p ~/.config/espanso/match
cat > ~/.config/espanso/match/base.yml <<'YAML'
matches:
- trigger: ":sig"
replace: "Best regards,\nAlex"
- trigger: ":today"
replace: "{{mydate}}"
YAML
espanso restart
espanso status
YAML indentation matters here. A malformed file can make an otherwise healthy installation look broken, so validate small changes incrementally. Start with plain text replacements before adding shell commands, forms, or dynamic values.
The second rough edge is OS permission handling. On macOS, espanso may need Accessibility permission to detect and replace text in other applications. Linux desktop environments can also behave differently depending on the display server and application toolkit. Test in a text editor, browser, terminal, and password field rather than assuming universal compatibility.
Before production use, watch out for:
- Sensitive fields: Do not expand secrets into password managers, authentication prompts, or applications that intentionally block simulated input.
-
Trigger collisions: Short triggers can fire unexpectedly inside code, URLs, or normal prose. Prefixes such as
:reduce accidental replacements.
For debugging, isolate the problem: check espanso status, inspect the generated logs, then disable all matches except one minimal trigger. That quickly separates installation, permission, and configuration failures.
Top comments (0)