boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
baltazar has quit [Ping timeout: 252 seconds]
baltazar has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
erdem has quit [Remote host closed the connection]
erdem has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
rcf has quit [Ping timeout: 265 seconds]
rcf has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
fitrh has joined #foot
fitrh_ has joined #foot
fitrh_ has quit [Client Quit]
fitrh has quit [Ping timeout: 240 seconds]
jarmo has joined #foot
<jarmo>
Greetings. I was here yesterday asking why "less" was working incorrectly together with foot. Came back to report, for the logs and others, what the issue was.
<jarmo>
The standard "stack*"-site solution to less 1. not clearing screen after exit and 2. retaining color is to use options -Xr. But in foot, this combo, or one of them, wreaks havoc. A working solution is to set options "--redraw-on-quit -R".
jarmo has left #foot [#foot]
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
MyNetAz has quit [Remote host closed the connection]
mtm has quit [Ping timeout: 244 seconds]
boomboxnation has joined #foot
MyNetAz has joined #foot
mtm has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
TommyJolly has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
<TommyJolly>
Thought I had a foot problem, but it's looking more like a coreutils problem. If dnkl and contributors are here, thanks for a great (and underrated) bit of software :)
TommyJolly has quit [Quit: Client closed]
trepatudo has quit [Ping timeout: 246 seconds]
boomboxnation has joined #foot
<dnkl>
TommyJolly: I'm here and hear you; you're welcome :)
emcconvi- has joined #foot
emcconville has quit [Ping timeout: 248 seconds]
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
Biolunar has quit [Quit: leaving]
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
Biolunar has joined #foot
haasn has quit [Ping timeout: 248 seconds]
haasn has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
ciara has quit [Remote host closed the connection]
ciara has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
birdisword has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
ls-alh has joined #foot
<ls-alh>
Hey everyone. Whenever I close a Foot terminal window, systemctl --user reports a failed unit, because it exits with code 1. How can I stop this? My system is degraded with 100 failed units, all from foot
ls-alh has quit [Ping timeout: 240 seconds]
boomboxnation has quit [Read error: Connection reset by peer]