Skip to content

Fix evil copy-mode - #670

Closed
ivanrg99 wants to merge 1 commit into
dakra:mainfrom
ivanrg99:3-evil-copy-mode
Closed

ivanrg99 wants to merge 1 commit into
dakra:mainfrom
ivanrg99:3-evil-copy-mode

Conversation

@ivanrg99

@ivanrg99 ivanrg99 commented Sep 1, 2026

Copy link
Copy Markdown

Keep copy mode active for Vim motions and allow ESC to recover from read-only insert state.

Keep copy mode active for Vim motions and allow ESC to recover from
read-only insert state.
dakra added a commit that referenced this pull request Sep 30, 2026
Entering copy or Emacs mode from evil insert state left insert state
active.  Insert state binds no printable keys, so j, k and other
motions hit the read-only fast-exit map, leaving copy mode and typing
the letter into the terminal.

ghostel-readonly-enter-hook runs after entering copy or Emacs mode.
evil-ghostel uses it to switch insert state to normal state, which
covers every entry path: C-c C-t, Emacs mode, prompt and link jumps,
mouse selection, and search / minibuffer landings.  Emacs state keeps
the fast exit.

The evil read-only elate suite covers C-c C-t and isearch from insert
state.  The word-boundaries suite, documented but never added, starts
each double-click in insert state and checks that the resulting visual
selection copies exactly the selected text.

Supersedes #670.
@dakra

dakra commented Sep 30, 2026

Copy link
Copy Markdown
Owner

Thanks and sorry for the delay.
While fixing #715 I remembered this PR and with #716 and #717 I think this one is not necessary anymore.

I'll close this for now but as I'm no evil user please report or re-open if there's still something missing.

@dakra dakra closed this Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants