caveman has quit [Remote host closed the connection]
cabal704 has quit [Ping timeout: 240 seconds]
c7s has joined #foot
Arnavion has quit [Ping timeout: 272 seconds]
Arnavion has joined #foot
cabal704 has joined #foot
cabal704 has quit [Client Quit]
xenrox has quit [Remote host closed the connection]
xenrox has joined #foot
c7s has quit [*.net *.split]
tomleb has quit [*.net *.split]
tomleb has joined #foot
c7s has joined #foot
zar_ has quit [*.net *.split]
zar has joined #foot
noteness has quit [*.net *.split]
kevr has quit [*.net *.split]
noteness has joined #foot
kevr has joined #foot
cbb has joined #foot
c7s has quit [Ping timeout: 256 seconds]
hgc has quit [Quit: hgc]
c7s has joined #foot
caveman has joined #foot
<sochotnicky>
I wonder why I keep seeing render: failed to load xcursor pointer 'text' error every time I switch into foot windows - I don't particularly care about cursors, the error is a bit annoying though :-)
<dnkl>
sochotnicky: foot is trying to set the xcursor pointer, but your cursor theme lack a pointer named 'text'
<dnkl>
In the master branch, we've added a fallback to 'xterm', which should fix this
<sochotnicky>
dnkl: I am actually not quite clear - sway's "seat xcursor_theme ..." is presumably only for XWayland? Or does that get used by foot too?
<dnkl>
That command also sets the XCURSOR_THEME variable, which foot does look at (since there's no Wayland generic way to communicate which xcursor theme to use)
<sochotnicky>
ah, right - OK, I guess that will be "it" then...
<dnkl>
Apparently, there's quite a few cursor themes missing 'text'. But they do have 'xterm'... Go figure...
<sochotnicky>
yeah, ty that seems to have worked (and my theme has text so not a big deal)
cabal704 has joined #foot
cvmn has joined #foot
cabal704 has quit [Ping timeout: 252 seconds]
cabal704 has joined #foot
cbb has quit [Ping timeout: 240 seconds]
cvmn has quit [Ping timeout: 240 seconds]
cvmn has joined #foot
cvmn has quit [Remote host closed the connection]
cabal704 has quit [Quit: WeeChat 3.4]
<caveman>
foot made it into gentoo's portage recently. nice.
<sochotnicky>
yeah, I assume that's why the folks also finally merged my fix for portage to update terminal title when running in foot :-)
<sochotnicky>
yeah, nothing too crazy - just a minor annoyance/quality of life thing
<caveman>
i guess that was in part to do with sway adopting foot as default terminal.
<caveman>
swaywm was already in portage. they got checkmated.
<sochotnicky>
hah, possibly. Then again - they could have also just changed the default config
<sochotnicky>
but it's not like foot is crazy hard to package up or has 10 level deep new dependency tree
<caveman>
true, but not worth the extra effort. adding food is easier imo.
<caveman>
foot*
<sochotnicky>
yup
<caveman>
plus, imagine the sorrow that dev must have every time he deleted 'foot' to write 'alacritty'? it's spritual torture.
cbb has joined #foot
<Lord>
hey dnkl i just discovered you also coded fnott
<dnkl>
Lord: yup :D
cabal704 has joined #foot
cabal704 has quit [Ping timeout: 252 seconds]
cabal704 has joined #foot
mcepl[m] has left #foot [#foot]
cabal704 has quit [Quit: WeeChat 3.4]
noteness has quit [Remote host closed the connection]
noteness has joined #foot
funcrab has joined #foot
funcrab has quit [Client Quit]
funcrab has joined #foot
<Nuc1eoN>
dnkl, hey I had recently asked if a scrollbar is on the roadmap for foot, and I had received the answer that it isn't. May I ask for the reasoning, if there is any? It is not that I arbitrarily wish to have a scroll bar, but it genuinely helps when scrolling a lot of output, e.g. when compiling a lot of programs in you terminal with lots of output.
<Nuc1eoN>
I find it not feasible to press Shift+PgUp and wait until it scrolls to the point. Am I missing something?
<Nuc1eoN>
After a few weeks of usage that seems to be the only gripe and pain point with foot for me, so I am interested if there is a background to this.