[vim/vim] do not copy writes to the '+' register to the '*' register (PR #18831)

13 views
Skip to first unread message

Corey Hickey

unread,
Nov 28, 2025, 6:09:03 PM11/28/25
to vim/vim, Subscribed

Before this change, writes to '+' get copied to '', but only under certain conditions. By default, this does not happen, because clipboard autoselect is enabled. Disabling autoselect (an option which should only apply to visual mode) results in normal-mode writes such as "+yy also going to the '' register.

This behavior is undocumented and untested; remove the behavior in order to make Vim's handling of these two registers be consistent.

fixes: #18830


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/18831

Commit Summary

  • 63b743b do not copy writes to the '+' register to the '*' register

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18831@github.com>

Corey Hickey

unread,
Nov 28, 2025, 7:48:23 PM11/28/25
to vim/vim, Push

@bugfood pushed 1 commit.

  • 6de3649 do not copy writes to the '+' register to the '*' register


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18831/before/63b743b856ad48432bbbf2ed1a6c8638db9a25c5/after/6de3649417196f8985dc8649b7b2766edba9e4f8@github.com>

Corey Hickey

unread,
Nov 28, 2025, 8:17:20 PM11/28/25
to vim/vim, Subscribed
bugfood left a comment (vim/vim#18831)

This is related to: #1516

In that issue, the author is using unnamedplus, whereas in my case, I am specifying the register.

With my change, unnamed and unnamedplus still seem to work ok, as verified by manual testing and also by relying on the automated tests


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18831/c3590775378@github.com>

Christian Brabandt

unread,
Nov 30, 2025, 4:26:31 AM11/30/25
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18831)

I think this makes sense, thanks.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18831/c3592384805@github.com>

Christian Brabandt

unread,
Nov 30, 2025, 10:22:48 AM11/30/25
to vim/vim, Subscribed

Closed #18831 via aa133f8.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18831/issue_event/21257267065@github.com>

Corey Hickey

unread,
Nov 30, 2025, 1:50:07 PM11/30/25
to vim/vim, Subscribed
bugfood left a comment (vim/vim#18831)

Thank you.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18831/c3593090787@github.com>

Reply all
Reply to author
Forward
0 new messages