ssh -Y user@host
(same behavior for ssh -X user@host
)y
anking in +
or *
registers is not effective, nor p
utting in them; indeed, after I attempted y
aking in them, they're still not listed in :registers
.If I run xterm-256color
in a GUI session on the host, +
and *
work. Indeed, when I'm in the office they do work.
And if I connect via SSH from a xterm-256color
on my computer, +
and *
don't work.
So I think the problem is unrelated to the terminal emulator, but to SSH. Indeed, I would have expected the observed behavior if I had not passed -X
nor -Y
.
9.0 (2022 Jun 28, compiled May 04 2023 10:24:44) Included patches: 1-1378, 1499
rxvt-unicode-256color
, but I've tried with xterm-256color
, and obeserve the same behaviorbash
IMPORTANT I'm connecting to the machine via SSH, so the value of $TERM
is the one on my system (Arch), not on Debian 12.
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Does this answer your question?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@nv-quan , I think it doesn't
ssh -X
as suggested by the last bullet point in the accepted answer.—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Then could it be a X-forwarding issue? Did you try copying to clipboard using another app through the ssh x-forwarding?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Would you suggest a way to use the clipboard via SSH that doesn't involve Vim?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Maybe you can try xclip
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
I worked from the office today, so I could try this:
xclip -o
-X
)xclip -o
At step 3, the selected text is correcly echoed.
At step 5, I get
Error: Can't open display: (null)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Ok, nevermind, it turns out IT department had disabled X11 forwarding :|
The solution was to add a whatever.conf
file under /etc/ssh/sshd_config.d/
with content
X11Forwarding yes
which has clearly nothing to do with Vim.
I suppose this thread can be closed, ... unless Vim could have a way to test for such a lack of x11 forwarding and throw a warning/error?
If not, I guess we can truly close this.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Closed #15111 as not planned.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.