summaryrefslogtreecommitdiff
path: root/modules/custom-buffer-file.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-11 09:12:32 -0500
committerCraig Jennings <c@cjennings.net>2026-05-11 09:12:32 -0500
commitea78a14339ca63e3a73976b9b68e35764423c733 (patch)
treef3985437fe85fb6eb039d6866f3628f49be49640 /modules/custom-buffer-file.el
parente221bf4c61be057c9408e4b11550d1e365ec065f (diff)
downloaddotemacs-ea78a14339ca63e3a73976b9b68e35764423c733.tar.gz
dotemacs-ea78a14339ca63e3a73976b9b68e35764423c733.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 'modules/custom-buffer-file.el')
0 files changed, 0 insertions, 0 deletions