<NickH>
AlmostSurelyRob: I too have both intel and nvidia graphics on my laptop
<NickH>
I simply blacklist kernel drivers for the nvidia chip and happily use the intel chip
<NickH>
Works a treat
thesock has joined #river
thesock has quit [Quit: Konversation terminated!]
vimproved has quit [Remote host closed the connection]
vimproved has joined #river
vimproved_ has quit [Remote host closed the connection]
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 255 seconds]
thesock has joined #river
angry_vincent has joined #river
selenebun has quit [Remote host closed the connection]
selenebun has joined #river
selenebun has quit [Remote host closed the connection]
selenebun has joined #river
selenebun has quit [Remote host closed the connection]
selenebun has joined #river
leopoldek has quit [Remote host closed the connection]
Szadek has quit [Quit: off]
Szadek has joined #river
Szadek has quit [Client Quit]
Szadek has joined #river
Szadek has quit [Quit: off]
Szadek has joined #river
Szadek has quit [Quit: off]
Szadek has joined #river
hspak has quit [Quit: Ping timeout (120 seconds)]
hspak has joined #river
Guest39 has joined #river
Guest39 has quit [Quit: Client closed]
Szadek has quit [Quit: off]
Szadek has joined #river
Dustee has joined #river
<Dustee>
hi, how can i disable border when there is only one window on a screen?
<novakane>
Dustee: you can't for now, you could write something with river status and layout protocol but it's a bit hacky currently
ThatGuestAgain has joined #river
<novakane>
maybe someone already wrote something but I'm not aware of it
hspak has quit [Quit: Ping timeout (120 seconds)]
hspak has joined #river
angle has left #river [#river]
<Dustee>
i just got an idea that i can achieve a similar result with `riverctl border-width 0` paired with `river-bsp-layout --inner-gap 1 --outer-gap 0 &`
<ThatGuestAgain>
There are two hacky ways with the layout manager I tried out: Let it place the border outside of the output (-1 -1 width+2 height+2) or let the layout manager call riverctl repeatedly. I ended up just accepting the border.
<Dustee>
however i lose the red border notification when i set them to 0
<ThatGuestAgain>
Currently my borders are the same color as the background color so they only get visible when windows overlap :)
<Dustee>
for me, the background color now serves as an inner border
<novakane>
well the way to do it would be using the layout protocol to know when there is only one window and then sending a command to make the border with a 0 width with the control protocol
<novakane>
that's not ideal for frame perfection though
<ThatGuestAgain>
That's what I meant above, except I used luatile and the shell command since I have yet to learn how to use protocols directly.
<novakane>
it will be way more easier once we have the new windows management protocol
<ThatGuestAgain>
I've already started learning Zig on the weekend to be ready to take rivertile (once it is the wm version) and adapt it to my needs. Unfortunatly manual memory management hurts my brain :D
<novakane>
hehe yeah no need to know too much about it for something like rivertile but still good to learn it for zig
<ThatGuestAgain>
Oh I am going to need it for the features I plan...
<novakane>
oh yeah already got some big ambitions? :P
<ThatGuestAgain>
Well... I have ideas how to reconcile river/awesome-like tags with somewhat manual layouts (not quite sway/bspwm-like but close) so yeah :)
<novakane>
can't wait for the new WM protocol we gonna have some cool clients for river
<ifreund>
yeah, I'm pretty excited too
<ifreund>
ThatGuestAgain: fwiw, I vaguely plan to make a demo wm in something higher level than Zig like lua
<ifreund>
I'd like to make writing wms as accessible as possible
<ThatGuestAgain>
Nice. Actually lua is the only language I'd dare to say I know well. (Not really an achievement with such a simple language I guess)
ThatGuestAgain has quit [Ping timeout: 256 seconds]
waleee has joined #river
Dustee has quit [Quit: Client closed]
TheAnachron has joined #river
TheAnachron has quit [Remote host closed the connection]
TheAnachron has joined #river
waleee has quit [Quit: WeeChat 4.1.2]
angry_vi` has joined #river
Corneliu1-Figgle has joined #river
TheAnachron has quit [*.net *.split]
angry_vincent has quit [*.net *.split]
Cornelius-Figgle has quit [*.net *.split]
wuyoli has quit [*.net *.split]
mattnite has quit [*.net *.split]
haasn has quit [*.net *.split]
haasn has joined #river
wuyoli has joined #river
mattnite has joined #river
thesock has quit [Remote host closed the connection]
wuyoli has quit [*.net *.split]
mattnite has quit [*.net *.split]
haasn has quit [*.net *.split]
mattnite has joined #river
haasn has joined #river
wuyoli has joined #river
Dustee has joined #river
TheAnachron has joined #river
Guest81 has joined #river
<Guest81>
anybody know how to set default output?
<Guest81>
i made riverctl rule-add HDMI-A-1 IT dont work
Guest81 has quit [Client Quit]
Guest64 has joined #river
Guest64 has quit [Client Quit]
Guest86 has joined #river
<Guest86>
was typo lol
<Guest86>
where to store a state for my command loop? it will cycle through command i need to store state somewhere
<ifreund>
Guest86: you can write to a file in /tmp for example
leopoldek has joined #river
Guest86 has quit [Quit: Client closed]
TheAnachron has quit [Quit: TheAnachron]
leopoldek has quit [Ping timeout: 252 seconds]
<leon-p>
I still plan on doing a wrapper library around the WM protocol and bindings in guile / python /whatever other high-level language I find fun that week, should be easy to build a good WM with that, in theory
<leon-p>
allthough I'll likely first experiment with a simple reference WM in C, as usual
leopoldek has joined #river
angry_vi` has quit [Remote host closed the connection]
angry_vi` has joined #river
angry_vi` has quit [Remote host closed the connection]
<leon-p>
FWIW I think doing certain things (i.e. multi-window pointer-resize with constraints) in high-level languages, especially functional ones, would be kinda miserable, so a helper library is pretty much needed IMO
<leon-p>
what I want to see (and maybe try) is using stack based concat languages for implementing WM logic
<leon-p>
or maybe even something more fun like APL or related
angry_vincent has joined #river
waleee has joined #river
Szadek has quit [Quit: off]
Szadek has joined #river
Dustee has quit [Quit: Client closed]
<ifreund>
that would be very cool to see indeed
<ifreund>
I think the draft protocol is almost to the point where it makes sense to start an implementation
<ifreund>
all the big questions are now answered afaik
<leon-p>
note that as soon as the river-side implementation is usable, there is a high chance I will bug you about features / clarifications
<gbrlsnchs>
ifreund: Will there be a blog post or something related to that new protocol? I'm totally out of loop but would love to learn more about what's being cooked for river
waleee has quit [Ping timeout: 252 seconds]
<leon-p>
gbrlsnchs: I plan on writing a reference WM in C and documenting it and the process in a blog-post, but that is not a small project, so it will take a while I think
notzmv has quit [Read error: Connection reset by peer]
angry_vincent has quit [Ping timeout: 255 seconds]
angry_vi` has joined #river
notzmv has joined #river
angry_vi` has quit [Remote host closed the connection]
angry_vincent has joined #river
dvzrv has quit [Quit: WeeChat 4.3.1]
dvzrv has joined #river
<gbrlsnchs>
leon-p: That sounds good, I really appreciate that! Are there any other references regarding the overall idea behind it? A README or something?
<leon-p>
gbrlsnchs: you can read the protocol itself (rwm branch on git). Wayland protocol extensions are generally self-documenting.
<gbrlsnchs>
gotcha, thanks! I'll take a look then
<leon-p>
the XML may seem a bit scary at first, but you'll get used to it quickly
<gbrlsnchs>
XML files are always scary, but alas xD
<leon-p>
a gui/tui browser for protocols would be kinda neat. There is a web based one, but I don't like its UI and I don't think you can add custom protocols to it so it's not really useful for server specific protocols like this one
<ifreund>
I also plan to write a blog post announcing the protocol that goes into a bit more detail when things are ready for people to actually play with on master branch
angry_vincent has quit [Ping timeout: 264 seconds]
<gbrlsnchs>
That sounds great, thank you folks!
CelestialCrafter has joined #river
<CelestialCrafter>
hey! is there any fakefullscreen in riverwm? and if theres not is there any way to get it at all?
CelestialCrafter has quit [Client Quit]
<leon-p>
CelestialCrafter: If my guess about what you mean w.r.t. "fakefullscreen" is true, then it would actually violate the xdg-shell protocol and as such is not something river likely will ever support I think
Guest49 has joined #river
Guest49 has quit [Client Quit]
CelestialCrafter has joined #river
<CelestialCrafter>
leon-p what's w.r.t?
<leon-p>
"with regards to"
<CelestialCrafter>
ah
CelestialCrafter has quit [Quit: Client closed]
<leon-p>
a workaround would be to run the application you want "fake fullscreened" in a nested compositor like cage
<leon-p>
unless you are running something graphics intensive there should be no noticeable performance hit