dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.18.1 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
mtm has quit [Ping timeout: 248 seconds]
mtm has joined #foot
andyrtr has joined #foot
ninewise has quit [Ping timeout: 260 seconds]
<runxiyu> Is there a command line utility that could utilize Foot's ability to display images?
<runxiyu> Occasionally I want to view an image but I feel like doing that just in my terminal
ninewise has joined #foot
bent_fingers has quit [Quit: Connection closed for inactivity]
<rockorager> runxiyu: https://github.com/hzeller/timg
NickH has quit [Remote host closed the connection]
<runxiyu> thanks
<runxiyu> cmake :(
sentriz has quit [Ping timeout: 244 seconds]
<runxiyu> aw sad, I can't install libavutil
NickH has joined #foot
sentriz has joined #foot
lbia has quit [Ping timeout: 248 seconds]
bent_fingers has joined #foot
Brazhh has joined #foot
<kode54> but it's a part of ffmpeg?
Brazhh has quit [Quit: WeeChat 4.3.5]
Brazhh has joined #foot
Brazhh has quit [Client Quit]
lbia has joined #foot
bent_fingers has quit [Quit: Connection closed for inactivity]
Biolunar has quit [Quit: brb]
Biolunar has joined #foot
alexherbo2 has joined #foot
<Lord> i tried playing a 1080p movie in mpv with sixel output but it was way too slow. is it normal ? (sixel may be inherently slow ?)
rcf has quit [Quit: WeeChat 3.8]
<dnkl> if you consider that using mpv with the sixel output is basically the same as transcoding the video, it's not _that_ slow
<dnkl> but yes, any terminal image format that doesn't send the image data out-of-band is slow
<dnkl> if possible, applications should cache the generated sixels so that they don't have to re-encode them every time they want them displayed
rcf has joined #foot
cbb has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
olndrxyz has quit [Read error: Connection reset by peer]
olndrxyz has joined #foot
olndrxyz has quit [Read error: Connection reset by peer]
olndrxyz has joined #foot
mtm has quit [Ping timeout: 246 seconds]
mtm_ has joined #foot
rcf has quit [Quit: WeeChat 3.8]
rcf has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
MegaM has joined #foot
<MegaM> hi
olndrxyz has quit [Ping timeout: 252 seconds]
olndrxyz has joined #foot
mtm_ has quit [Ping timeout: 246 seconds]
<MegaM> I have a small problem with Foot, the base command I type is always repeated on the output, is it a Foot problem or do I have to search elsewhere?
<MegaM> it look like this:  https://pic.infini.fr/ybBbNQGO/KgFntW1D.png
mtm has joined #foot
<dnkl> MegaM: what does 'infocmp' say?
<dnkl> are you using 'screen'? Does the issue reproduce outside screen? Which outer terminfo are you using?
<MegaM> I am not using screen
<dnkl> then use foot's own terminfo, not screen's
<MegaM> I do not know what a terminfo is
<j`ey> MegaM: what does `echo $TERM` show?
<MegaM> I just install hyprland and  install foot with the package manager (pikaur, for archlinux)
<dnkl> try googling it. There's an option in foot to set it, but the defaults should be good. My guess is your shell config overrides it
<MegaM> screen-256color
<MegaM> foot-terminfo is installed
<MegaM> Ok i will search in this way
<MegaM> thank you
<j`ey> dnkl: off topic but, is pixman immediate? or is there a 'draw now' call or something?
<dnkl> j`ey: immediate. It manipulates a raw pixel buffer directly. It's also not automatically connected to any actual output. You have to somehow attach it yourself to something that can display it
<dnkl> in my applications, I have a wayland buffer pointing to the same backing buffer as my pixman buffers
<MegaM> I had "export TERM=screen-256color" in .zshrc, I change for foot and it works :)
<j`ey> is it double buffered?
<j`ey> MegaM: just dont set it at all is better!
<j`ey> or does the wayland damage stuff mean you don't need to do double buffering
<MegaM> it works too if I didn't set it too, I havn't touch my configuration for yars I do not remember why I put this line in the first place
<j`ey> https://codeberg.org/dnkl/foot/issues/478 this issue looks interesting to me
<dnkl> j`ey: Wayland damage had nothing to do with double buffering
<dnkl> it's something you have to do yourself using multiple pixman buffers
<j`ey> yeah I think I mis-spoke/mis-understood something. This part was clearer "Foot currently relies heavily on the compositor allowing us to re-use shm surfaces in the next frame."
xenrox has quit [Ping timeout: 260 seconds]
MegaM has quit [Quit: Client closed]
MegaM has joined #foot
olndrxyz has quit [Remote host closed the connection]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
olndrxyz has joined #foot
olndrxyz has quit [Ping timeout: 265 seconds]
ninewise has quit [Remote host closed the connection]
ninewise has joined #foot
MegaM has quit [Quit: Client closed]
olndrxyz has joined #foot
olndrxyz has quit [Remote host closed the connection]
olndrxyz has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
ninewise_ has joined #foot
ninewise has quit [Ping timeout: 260 seconds]
mtm_ has joined #foot
mtm has quit [Ping timeout: 272 seconds]
mtm has joined #foot
mtm_ has quit [Ping timeout: 246 seconds]
xenrox has joined #foot
MegaM has joined #foot
MegaM has quit [Ping timeout: 256 seconds]
cbb has quit [Quit: cbb]
ninewise_ has quit [Remote host closed the connection]
ninewise_ has joined #foot
alexherbo2 has joined #foot
alexherbo2 has quit [Ping timeout: 256 seconds]
olndrxyz has quit [Remote host closed the connection]
olndrxyz has joined #foot