<Pound_Hash>
Can the colors for scrollback search be customized?
cvmn has joined #foot
<Pound_Hash>
The text box in the bottom right is a black rectangle for me until I type something that isn't found, then it turns red and I can see it.
Nulo has quit [Ping timeout: 272 seconds]
Nulo has joined #foot
cvmn has quit [Remote host closed the connection]
cvmn has joined #foot
cvmn has quit [Remote host closed the connection]
cvmn has joined #foot
cvmn has quit [Read error: Connection reset by peer]
cvmn has joined #foot
Nulo has quit [Ping timeout: 240 seconds]
Nulo has joined #foot
Pound_Hash has quit [Ping timeout: 244 seconds]
Pound_Hash has joined #foot
cvmn has quit [Remote host closed the connection]
cvmn has joined #foot
cvmn has quit [Remote host closed the connection]
cvmn has joined #foot
rv178 has joined #foot
<rv178>
hello
<rv178>
how do I get image support in foot terminal
cvmn has quit [Remote host closed the connection]
noteness has quit [Remote host closed the connection]
<manio>
rv178: foot has support for sixel
cvmn has joined #foot
rv178 has quit [Remote host closed the connection]
rv178 has joined #foot
rv178 has quit [Client Quit]
rv178 has joined #foot
rv178 has quit [Client Quit]
rv178 has joined #foot
caveman has joined #foot
cvmn has quit [Remote host closed the connection]
rv178 has quit [Quit: Leaving]
caveman has quit [Write error: Connection reset by peer]
caveman has joined #foot
Pound_Hash has quit [Quit: Pound_Hash]
caveman has quit [Remote host closed the connection]
caveman has joined #foot
caveman has quit [Ping timeout: 268 seconds]
caveman has joined #foot
cvmn has joined #foot
cvmn has quit [Ping timeout: 268 seconds]
noteness has joined #foot
<dnkl>
Arsen: I think there are a couple of issues involved with your scroll-up-while-making-a-selection crash
<dnkl>
first, why do we get disconnected? Probably because we're flooding the wayland socket with requests. Not sure yet with what, but probably related to the selection
<dnkl>
second, we end up getting a pointer motion event *after* having been disconnected, while shutting down. Might be left overs from before the disconnected (i.e. a queued event). So we have two options here: see if we can do better at flushing events before handling the EPOLLHUP on the wayland socket. Or, don't try to send wayland requests while shutting down if the wayland socket is dead
<dnkl>
hmm, I'm guessing it's actually the compositor that's flooding the socket with pointer motion events. Foot is too slow to handle them while updating the selection. At least in debug builds. Haven't tested a release build yet
<dnkl>
and foot is slow because we're not handling large selections well
<dnkl>
ok, so each time we render a frame, we walk the *entire* selection to mark those cells as being selected (to ensure we get the proper coloring). This is obviously bad. The solution is to only walk the *visible*, selected cells
caveman has quit [Remote host closed the connection]
caveman has joined #foot
avane has quit [Ping timeout: 240 seconds]
avane has joined #foot
talismanick has joined #foot
talismanick has quit [Ping timeout: 272 seconds]
cabal704 has joined #foot
cabal704 has quit [Quit: WeeChat 3.5]
noteness has quit [Remote host closed the connection]
noteness has joined #foot
noteness has quit [Remote host closed the connection]
noteness has joined #foot
lack has joined #foot
<lack>
Hi! I'm pretty new to Wayland&Foot, but trying to figure out a font issue... I'm looking for the right way to tell foot to use the old X11 "6x13" font. Any tips? Fedora 36 if that matters...
<lack>
I can find the file on disk; it's '/usr/share/X11/fonts/misc/6x13.pcf.gz' - I just have no idea how to tell foot to use that font.
<dnkl>
run fc-list and look for that file. You should see its fontconfig name (which is what you need to use in foot) as well
<lack>
Hmmm... not there in the fc-list output! That's probably why it's hard to find.
<lack>
I guess I'll have to figure that out...
<lack>
Another weird issue is that in most other terminals, 'ls' has color output. In 'foot' it does not, but if I run 'ls --color' it does. Any tips on fixing that up?
<Arsen>
so, wait for that to land, and in the meanwhile, just call ``eval "$(TERM=xterm-256color dircolors)"'' in your bashrc
<lack>
Cool! I'm running coreutils-9.0-5.fc36.x86_64. But I adde that eval line, and I saw the LS_COLORS in my env, but even then just running `ls` didn't show dircolors unless I also did `ls --color=always`
<Arsen>
huh, that's strange then
<lack>
Agreed! Also, when I set `ls --color=auto' it does nice color output even if LS_COLORS isn't set.
Pound_Hash has joined #foot
<Pound_Hash>
quit
<Pound_Hash>
quit
Pound_Hash has quit [Quit: Pound_Hash]
Pound_Hash has joined #foot
<Pound_Hash>
What's the simplest way of reloading `foot.ini` when running in server/client mode?
<Pound_Hash>
Currently, if I edit `foot.ini` I have to either reboot the machine to load the changes, or else open `foot` rather than `footclient`.
<Pound_Hash>
I would rather reload the changes in the server and just run `footclient` each time
Guest2916 has quit [Quit: Using Circe, the loveliest of all IRC clients]
talismanick has joined #foot
<Pound_Hash>
What is "mouse tracking"? I can't find an explanation for it.