<armin>
so sometimes, something weird happens in a terminal while i'm focused on other things, after my prompt, and i don't know why that happens. it looks like this: " ;7;13~;7;13~;7;13~;7;13~;7;13~" - anyone a clue what i (the human in front of the computer who should know what they have pressed, i admit it) has typed?
cbb has joined #foot
<dnkl>
armin: you're probably holding down shift, or control, while hitting enter, or backspace, or similar
<rumpelsepp>
Currently I am experimenting with OSC stuff, since I need to improve my SSH experience. I want that my clipboard works over ssh. I discovered that tmux has support for this and I can configure neovim to use this. tl;dr: In tmux I have set "set-option -g set-clipboard on".
<rumpelsepp>
This correctly sets the system clipboard: echo "foo" | tmux load-buffer -w -
<rumpelsepp>
According to the docs, tmux requests a clipboard update from the terminal via OSC 52: tmux refresh-client -l
<rumpelsepp>
This doesn't work. foot pastes the OSC stuff in shell's commandline.
<rumpelsepp>
Can anybody help me figuring out of this is a tmux issue, foot issue, or some silly mistake on my side? 🙂
<rumpelsepp>
Hmm. Still something is missing. tmux refresh-client -l doesn't print OSC data to the terminal prompt any more, but the clipboard is not read as well.
<rumpelsepp>
yeah, setting the tmux clipboard via OSC52 and tmux refresh-client -l seems to do nothing. Did a few more tests with clean config and such.
<cbb>
rumpelsepp: the first thing to try would be to take tmux out of the picture and see if you can set the clipboard in just foot
<cbb>
if you can, it's probably a tmux configuration problem
<rumpelsepp>
I might have caused some confusion. Setting works. Reading is the problem. tmux refresh-client should request the content of the system clipboard via OSC52 and set the tmux clipboard to the content of the system clipboard.
<rumpelsepp>
But yeah, will quick check.
<rumpelsepp>
foot responds to: bash -c "echo -en \"\033]52;c;?\a\""
<rumpelsepp>
hmm. tmux issue?
gtms has quit [Remote host closed the connection]
<cbb>
rumpelsepp: yeah, foot should respond to that request
<cbb>
what are you trying to in general?
<cbb>
configure tmux?
<cbb>
or use OSC 52 for something in particular?
<cbb>
trying to do*
<rumpelsepp>
My use case is using the system (wayland) clipboard over SSH in neovim. I always use tmux everywhere and in theory tmux has support for OSC52.
<rumpelsepp>
But yeah, I couldn't get the pasting stuff working. Would be helpful since I often pipe data around and I misuse the clipboard for exchanging data. 😀
<cbb>
rumpelsepp: I've been meaning to configure all that stuff in tmux for a while too
<cbb>
I also use tmux everywhere, but I've been relying on wl-copy until now
<rumpelsepp>
Configuring tmux is done with only "set-option -g set-clipboard on"
<rumpelsepp>
Should (tm) all work out of the box. It does indeed for the copy case.
<cbb>
yeah, I've played around with it before, but never enabled it permanently
<cbb>
I'll look into it more and let you know how it turns out
<rumpelsepp>
Yeah, with this I could do `tmux refresh-client -l && tmux save-buffer -` and I have the contents of my clipboard available over ssh.
<rumpelsepp>
Nice thanks!
<cbb>
the app I care about mostly is about to merge built-in support for OSC 52 copy/paste, so I was going to be doing ti soon anyway
<cbb>
it*
<rumpelsepp>
seems to be a foot issue. It works on alacritty.
<cbb>
you're not sending OSC 52 sequences from an unfocused window by any chance are you?
<rumpelsepp>
No, I am typing this manually, so the window is focused.
amk has quit [Remote host closed the connection]
<rumpelsepp>
yep. even works in vim with my config
<dnkl>
rumpelsepp: can you dump the sequences sent by tmux? Enable LOG_ENABLE_DBG in osc.c, do a debug build, and run foot with "foot -d debug"
<rumpelsepp>
sure. Probably tomorrow, I am off this evening, doing my swimming. 🙂
<dnkl>
No worries. I might be able to test myself tonight.
novakane has quit [Quit: WeeChat 3.3]
Lord has joined #foot
novakane has joined #foot
amk has joined #foot
pflm has quit [Ping timeout: 246 seconds]
pflm has joined #foot
diniwed has joined #foot
diniwed has quit [Ping timeout: 264 seconds]
diniwed has joined #foot
<cbb>
dnkl: apparently xterm replies to OSC sequences with whichever terminator was used in the requsts
<cbb>
I wonder if we could always emit BEL without any negative consequences?
<cbb>
The usual concerns about it being non-standard may not be so bad, considering there's no terminal->client standard
novakane has quit [Quit: WeeChat 3.3]
pflm has quit [Remote host closed the connection]
cbb has quit [Quit: WeeChat 3.3]
<diniwed>
dnkl: to let you know that I eventually got the colour emojis to work ...