dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.10.1 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
ericonr has quit [*.net *.split]
psnszsn has quit [*.net *.split]
chrisppy has quit [*.net *.split]
sterni has quit [*.net *.split]
novakane has quit [*.net *.split]
andrea has quit [*.net *.split]
coder_kalyan has quit [*.net *.split]
ddevault has quit [*.net *.split]
travankor has quit [*.net *.split]
psnszsn has joined #foot
ddevault has joined #foot
novakane has joined #foot
sterni has joined #foot
sterni has quit [Signing in (sterni)]
sterni has joined #foot
andrea has joined #foot
chrisppy has joined #foot
coder_kalyan has joined #foot
ericonr has joined #foot
st3r4g has quit [Quit: おやすみ]
helby has joined #foot
cherti has quit [Ping timeout: 268 seconds]
cherti has joined #foot
<coder_kalyan> dnkl: just to check, do you plan to make a new patch release soon regarding the osc8 fixes? I'm currently running git master but would prefer to switch back to an official release
<coder_kalyan> if not thats totally fine, it's not a huge issue
<coder_kalyan> dnkl: just copied my foot config from my desktop to my laptop, and I noticed the text was much too large (had to change font size from 12 to 8 to get a similar size). Both displays are 1080p but obviously different size/DPI. Is this expected behavior?
<dnkl> coder_kalyan: I do plan on making a patch release soon. As soon as I have enough spare time to go through tagging etc. So hopefully before the end of this week.
<coder_kalyan> and/or is there a way of specifying something resilient to different monitor sizes?
<coder_kalyan> oh, cool. thanks a lot
<dnkl> Foot adapts to your monitor'd DPI, yes.
<dnkl> So if they are at different viewing distances
<dnkl> Font will look different
<dnkl> But if they are at the same viewing distances, the font should have the exact same size
<dnkl> See dpi-aware in foot.ini
<rj1> foot is the best its the very very best o wow i love it so muuuuuuuch
<coder_kalyan> lol yeah its a emulator :)
<coder_kalyan> dnkl: ok, i see. just checked and it does appear that the DPI is being correctly compensated but my laptop has less real estate and closer viewing distance
<dnkl> Foot automatically turns dpi-awareness off, if you enable output scaling. Or you can manually turn it off in the config
<coder_kalyan> turning it off helped, but caused some other side effects. ill play around with it tomorrow, thanks
travankor has joined #foot
sterni has quit [Quit: WeeChat 2.9]
sterni has joined #foot
ty1opom2 has joined #foot
<ty1opom2> thoughts on servo ?
<ty1opom2> would it be worth using servo as a webengine for a gtk4 web browser?
st3r4g has joined #foot
ty1opom2 has quit [Ping timeout: 256 seconds]
ty1opom2 has joined #foot
<Lord> Servo is quite rough
st3r4g has quit [Quit: おやすみ]
<ty1opom2> okay just tried servo, yeah thats broken
<ty1opom2> ;(
ty1opom2 has quit [Quit: Client closed]
st3r4g has joined #foot
an3223 has joined #foot
<an3223> strange things are a foot
<an3223> what's up with the keys sent on Ctrl+0 when [key-bindings] font-reset=
<an3223> showkey -a shows a lot of keys sent from foot
<an3223> but with Ctrl+0 unbound in alacritty it's just "48 0060 0x30"
<dnkl> an3223: Alacritty doesn't include any modifier (ctrl, alt, shift etc) information for many key combos. Foot does
<dnkl> an3223: foot operates in a mode XTerm calls "modifyOtherKeys=1"
<dnkl> Google that for more information
<an3223> hmm okay
<an3223> dnkl: i'm guessing there isn't a way to configure this behavior?
<dnkl> an3223: no. Why do you want/need ctrl+0 to send exactly the same thing just "0" does?
hspak has quit [Ping timeout: 268 seconds]
<an3223> dnkl: i thought it was causing weird behavior in vim, but i can't seem to reproduce the behavior anymore :/
<an3223> it used to be that Ctrl+0 broke my insert mode remaps until i restarted vim
<dnkl> an3223: could perhaps be related to https://github.com/vim/vim/issues/9014
<dnkl> It's a long thread, but bottom line is we've done what we can in foot to "help" vim. The rest is up to them
<dnkl> an3223: if you're on foot >= 1.10.0, you can add the t_TI/t_TE options to your vimrc, as described here: https://codeberg.org/dnkl/foot/pulls/791
<an3223> dnkl: okay i am able to reproduce the issue again (i was being silly before and hitting the wrong keybind), im on foot 1.10.1, and adding those t_TI/t_TE options to my vimrc does _not_ fix the issue
<dnkl> an3223: and you're sure you entered them correctly? Including the initial, literal, ESC?
<an3223> err
<dnkl> (i.e selecting and copy-pasting will likely not work)
<an3223> okay fixed lol
<an3223> dnkl: thanks for the help :)
<dnkl> Np :)
<dnkl> I was hoping the vim devs would finish and close the bug soon:ish. But doesn't look like that's going to happen. So, guess I'll update foot's wiki with the t_TI/TE workaround...
<an3223> i think you can replace the escape characters with \<Esc> so they can be copy+paste-able, that's how i have it in my vimrc
<dnkl> an3223: thanks, I knew there was a way, just didn't remember it...
teraflops has joined #foot
an3223 has quit [Ping timeout: 276 seconds]
st3r4g has quit [Quit: おやすみ]
st3r4g has joined #foot
st3r4g has quit [Quit: おやすみ]
an3223 has joined #foot
st3r4g has joined #foot
an3223 has quit [Ping timeout: 276 seconds]