<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...
<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>
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