diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-11 09:12:32 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-11 09:12:32 -0500 |
| commit | 0103242a9da9dccd030f5ba21f2e9212f2ed18b9 (patch) | |
| tree | df4757e869460237a9cddd9e8462be8ab159ecec /tests/test-system-lib-executable-exists-p.el | |
| parent | 13d6cf010d8df12eed44a8eaf485128253fcb07b (diff) | |
| download | dotemacs-0103242a9da9dccd030f5ba21f2e9212f2ed18b9.tar.gz dotemacs-0103242a9da9dccd030f5ba21f2e9212f2ed18b9.zip | |
fix(ui-config): use the writeable cursor color in a live vterm
`vterm-mode' sets `buffer-read-only', so `cj/set-cursor-color-according-to-mode' painted the cursor with the read-only color (orange) whenever point was in a vterm. That includes the live terminal, not just `vterm-copy-mode'. But a live terminal takes input: keystrokes go to the process, not the buffer. So a live vterm now reports `unmodified' instead. `vterm-copy-mode' still reports `read-only': there it really is a read-only Emacs buffer the user navigates, and the orange cursor is the right signal.
I pulled the state cond out of `cj/set-cursor-color-according-to-mode' into `cj/--buffer-cursor-state' so it's unit-testable without a real frame or `set-cursor-color'.
Diffstat (limited to 'tests/test-system-lib-executable-exists-p.el')
0 files changed, 0 insertions, 0 deletions