dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.11.0 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
<funcrab> Nuc1eoN, Interesting. It's true that keys can't be used to specify pixels as quickly and seamlessly as a mouse can.
<funcrab> I hadn't thought of the perspective that it's hard to use the keyboard to check logs when there's a lot of output.
Oleg has quit [Ping timeout: 256 seconds]
Oleg has joined #foot
funcrab has quit [Quit: WeeChat 3.4]
c7s has quit [Ping timeout: 272 seconds]
cabal704 has joined #foot
cabal704 has quit [Client Quit]
cabal704 has joined #foot
cabal704 has quit [Client Quit]
cabal704 has joined #foot
cabal704 has quit [Client Quit]
<Nuc1eoN> Im compiling a lot of packages on a daily basis, so that is why I am missing such a functionality, and often revert back to urxvt for such cases :)
noteness_ has joined #foot
noteness has quit [Ping timeout: 240 seconds]
<dnkl> Nuc1eoN: the major reason is there's hasn't been much interest in it.
<dnkl> There are technical reasons as well though
<dnkl> First, the feature was never intended to, or designed for, being a scrollbar
<dnkl> For example, being a small box that indicates your scrollback position is just its default variant
<dnkl> It can also be configured to be always at the top, showing a percentage number
<dnkl> And a couple of other variants
<dnkl> Furthermore, it doesn't allocate any screen estate, it just renders on top of the grid
<dnkl> Meaning, you wouldn't be able to scroll by clicking somewhere outside the indicator
<dnkl> I.e, we _could_ implement "something", but it would be with limitations
<dnkl> Only usable with the default format of the indicator, and only by dragging it
<dnkl> And, someone would have to write a non-trivial chunk of code...
<dnkl> Nuc1eoN: btw, I see you're having fun with tmux and theme.sh...
<rj1> i really love foot..
<dnkl> Fwiw, I usually "search" for the prompt, to jump quickly between commands in the scrollback. Obviously doesn't work if your looking at a single large log file...
Guest69 has joined #foot
<Guest69> Hi
<Guest69> Is it possible to add internal paddings like here?
<Guest69> manio: Thanks
Guest69 has quit [Quit: Client closed]
cbb has joined #foot
cvmn has joined #foot
Nulo has quit [Ping timeout: 272 seconds]
cabal704 has joined #foot
cabal704 has quit [Client Quit]
cabal704 has joined #foot
cvmn has quit [Ping timeout: 240 seconds]
Nulo has joined #foot
cvmn has joined #foot
cabal704 has quit [Quit: WeeChat 3.4]
cvmn has quit [Ping timeout: 240 seconds]
cabal704 has joined #foot
cabal704 has quit [Quit: WeeChat 3.4]
kayw_ has left #foot [peace out]
cabal704 has joined #foot
cabal704 has quit [Client Quit]
c7s has joined #foot
cabal704 has joined #foot
cabal704 has quit [Quit: WeeChat 3.4]
cabal704 has joined #foot
cabal704 has quit [Ping timeout: 252 seconds]
cabal704 has joined #foot
c7s has quit [Ping timeout: 252 seconds]
cabal704 has quit [Ping timeout: 252 seconds]
ksynwa has joined #foot
<ksynwa> Had a question related to yambar if that is okay. I am using it with i3wm. Recently updated to 1.8.0 and for some reason the workspace indicator disappeared. From reading the changelog I can't figure out what to do about it.
<ksynwa> Any idea what I am doing wrong here?
<ksynwa> Actually nevermind. It seems to be something else. Just occured to me that I should be looking at the logs.
<ksynwa> This is the error message: err: modules/i3.c:94: workspace reply/event without 'name' and/or 'output', and/or 'focus' properties
<dnkl> ksynwa: let me take a look at the changes we've done. Could be we've introduced something Sway-only.
<dnkl> (btw, there's #yambar - granted, a bit empty atm)
cabal704 has joined #foot
<ksynwa> dnkl: I will join there in case you wanted to post something related to this. I am looking at the code too so if I find something I will post there.
ksynwa has left #foot [WeeChat 3.4]
c7s has joined #foot
cabal704 has quit [Quit: WeeChat 3.4]
cabal704 has joined #foot
cabal704 has quit [Client Quit]
<Nuc1eoN> dnkl, thanks for the explanation, I imagine it would require some effort yeah, but at least you now have some genuine feedback about it, and that there is a use case for it.
<Nuc1eoN> dnkl, heh wel well how did you find out about me theme.sh debacle :P
<Nuc1eoN> Sadly it won't be fixed, as both develoeprs argue they are doing the right thing :D
<Nuc1eoN> But the good news is, it only affects konsole, so I do not really care anymore:P
<Nuc1eoN> (actually it might have implications outside of konsole too though, but thats another story)
<dnkl> Nuc1eoN: foot was being mentioned there somewhere, and I occasionally look for foot related issues
<dnkl> fwiw: I'm completely with zsh4h on this one...
<Nuc1eoN> dnkl, fwiw me too, and I have also expressed that opinion in the theme.sh bug report in the end
<Nuc1eoN> the z4h guy actually knows his stuff, I mean he is also the author of powershell10k
<Nuc1eoN> The theme.sh dev took it like a "personal attack" for some reason, but imo the z4h dev was really clear and concise about the whole thing :)
<Nuc1eoN> He literally wrote z4h is acting "pathological" and "disingenuous" lol
<dnkl> feels like the theme.sh dev doesn't really understand the issue (or doesn't want to understand)
<dnkl> he also must not use ssh himself :)
<dnkl> s/must/can't be/
<Nuc1eoN> > "You cannot assume that if TMUX is not set, then the TTY is not tmux. You need to ask the TTY by sending it a DA."
<Nuc1eoN> I absolutely agree with this.
<dnkl> yup, preferably that, or _at least_ query terminfo. Only relying on env vars is... not good
c7s has quit [Quit: c7s]
cabal704 has joined #foot
cbb has quit [Quit: WeeChat 3.4]
cabal704 has quit [*.net *.split]
xenrox has quit [*.net *.split]
Biolunar has quit [*.net *.split]
ericonr has quit [*.net *.split]
cabal704 has joined #foot
xenrox has joined #foot
Biolunar has joined #foot
ericonr has joined #foot
cabal704 has quit [Quit: WeeChat 3.4]