dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.8.2 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #foot
trylletre has joined #foot
<rumpelsepp> hey hey. One more questions according OSC 9 and notifications (it might be a more general one). tmux seems to strip the OSC9 messages. I read somewhere that it is possible to wrap the message into another message that tmux lets it through. But I could not find it… Any hints? :)
<craftyguy> anyone have OSC 52 working with tmux in foot? seems like it just copies the first time
sosodank has joined #foot
<sosodank> hey @dknl, how much interest would you have in a somewhat platform-dependent means of accelerating terminal/app interaction, though only when on the same machine?
<sosodank> like where on your priority list would that kind of experimentation land
<sosodank> @dnkl, argh, not @dknl
<craftyguy> actually, copy works with tmux if I switch focus away from foot and move it back each time
<craftyguy> if I leave foot focused, subsequent attempts to copy don't update the clipboard
<craftyguy> I filed an issue, but apologize ahead of time if this isn't a foot bug.. I'm having trouble finding another terminal app that can do OSC 52 to see if the same happens there too
novakane has joined #foot
<dnkl> sosodank: besides bug fixes I don't have much of a todo-list atm. I'm mostly trying to catch up on my other projects. So yeah, sounds interresting. Have much though have you given it? I.e. do you already have something you want to try, or where are we?
<dnkl> rumpelsepp: craftyguy: you need to wrap the OSCs inside a DCS, *and* escape all ESCs
<dnkl> i.e. "\e]9;hello world\e\\" becomes "\ePtmux;\e\e]9;hello world\e\e\\\e\\"
<dnkl> one can also use BEL instead of ST in the inner OSC, in which case the above becomes "\ePtmux;\e\e]9;hello world\a\e\\"
<dnkl> is there really no native OSC-52 support in tmux?
<testuser[m]> dnkl: for htop did you just guess the color it was using or is there some other accurate way to do it ?
<dnkl> craftyguy: hmm, perhaps that's what you _are_ using... let me take a closer look at your bug report
<dnkl> testuser[m]: I just guessed. Otherwise you need to trace all the escape sequences it's sending...
<dnkl> testuser[m]: but you can run something like neofetch to get all your 16 base colors on screen, and then do a side-by-side comparison
<testuser[m]> ok thanks!
bisco_ has quit [Remote host closed the connection]
novakane has quit [Quit: WeeChat 3.2]
novakane has joined #foot
<arolle> Is there any convenient way to adjust all running footclient's base16 colorscheme (without a restart)?
<dnkl> arolle: pywal maybe?
<sosodank> well so i had to rip out my use of posix's open_memstream
<sosodank> in the scrotumtightening effort to run on windows
<sosodank> so now i've got these big-ass flat buffers and it's like so why am i copying buffer to buffer, exactly
<sosodank> https://github.com/dankamongmen/notcurses/issues/1822 so this would seem to apply even more now
<sosodank> i'm just looking for someone who's down to use the app->pty pipe as a launchpad for some bareback-ass shared memory plus semaphores
<sosodank> but if you think it's stupid and overengineered, i can't quite disagree
<arolle> dnkl: Thanks for the pointer. It seems that writing the OSC's to the respective tty/pty will do.
<dnkl> sosodank: it doesn't _sound_ over engineered, yet :)
<dnkl> after https://codeberg.org/dnkl/foot/issues/639#issuecomment-242595, it would be interresting to see what kind of performance we can get by bypassing the kernel
<dnkl> but let me read through the issue you mentioned, and get back to you. Rumours has it I'm on vacation, and supposedly I'm going kayaking today
birger has joined #foot
st3r4g has joined #foot
st3r4g has quit [Quit: おやすみ]
kmarius has quit [Ping timeout: 252 seconds]
kmarius has joined #foot
novakane has quit [Quit: WeeChat 3.2]