palanix has quit [Remote host closed the connection]
palanix has joined #river
palanix_ has joined #river
palanix has quit [Ping timeout: 252 seconds]
palanix_ is now known as palanix
nemoto has quit [Read error: Connection reset by peer]
nemoto has joined #river
Viapix has joined #river
Viapix has quit [Client Quit]
notzmv has quit [Ping timeout: 252 seconds]
<aktina>
yambar, but now the developer has archived it, so I need to find a sane alternative (not waybar, maybe my config is wrong but it takes long time to start up) or like yambar developer get used to not having any status bar (I rarely use it, like, sometimes I check to see how many apps I have kept open in monacle layout
notzmv has joined #river
ccha has quit [Quit: WeeChat 4.7.0]
ccha has joined #river
aryak has quit [Ping timeout: 248 seconds]
notchoc has quit [Ping timeout: 276 seconds]
aktina has quit [Ping timeout: 276 seconds]
notchoc has joined #river
aktina has joined #river
aryak has joined #river
aryak has quit [Ping timeout: 255 seconds]
notchoc has quit [Ping timeout: 255 seconds]
aktina has quit [Ping timeout: 252 seconds]
siaal_ has joined #river
siaal has quit [Ping timeout: 272 seconds]
siaal_ is now known as siaal
<leon-p>
you'll get used to having none quite fast. Most things displayed on status bars are fairly useless anyway
<LarstiQ>
time & date at a glance plus which tags my windows are on are kinda important to me
<LarstiQ>
battery level too though less often
<Nickli>
battery level of my UPS would be something
<leon-p>
I find tags to be only relevant when I am switching between them, so I have a tag popup which appears whenever something about tags changes and then disappears again
<LarstiQ>
leon-p: yeah I use that too but I apparently have more of a need to know when I'm not switching
siaal_ has joined #river
siaal has quit [Ping timeout: 248 seconds]
siaal_ is now known as siaal
siaal has quit [Ping timeout: 252 seconds]
siaal_ has joined #river
siaal_ is now known as siaal
siaal has quit [Ping timeout: 248 seconds]
siaal has joined #river
nemoto has quit [Remote host closed the connection]
notchoc has joined #river
aryak has joined #river
aktina has joined #river
kansei has quit [Ping timeout: 255 seconds]
kansei- has joined #river
kansei- is now known as kansei
kansei is now known as Guest8085
Viapix has joined #river
Viapix has quit [Client Quit]
<bwbuhse>
I haven’t used a bar in a year or so, just river-tag-overlay and my own clock application to have a clock visible, but I think I might go back to a bar with my rwm wm
<bwbuhse>
but only to have a clock, because I’m tired of my clock being in front of things I want to see :)
siaal has quit [Ping timeout: 276 seconds]
siaal has joined #river
<gbrlsnchs>
I currently have a keybind to show me a notification with date, time and current focused window. I'd rather have a bar though, but no time to config one at the moment. I wonder if it's easy to write one geared towards my own WM...? I have zero experience with writing bars.
<ifreund>
the protocol makes it easy for your WM to position a surface it creates whereever it likes without dealing with the complexity of layer shell
<ifreund>
unfortunately, rendering text and whatnot to a surface in the first place isn't that easy
<ifreund>
what language are you using?
<gbrlsnchs>
At the moment, C
<gbrlsnchs>
I was considering a Zig rewrite though
<Nickli>
would be nice to see a pane based WM like Herbsluftwm or the windows thingy
<ifreund>
In C i think cairo is probably the easiest way to render text and simple shapes to a surface
<ifreund>
swaylock and swaybar use cairo iirc if you want an example
<gbrlsnchs>
ifreund: Hmm gotcha. I will take a look on how to do that. Would fcft serve that purpose as well?
<ifreund>
yes, fcft works great too I'm sure
<ifreund>
it only does font rendering not drawing shapes though
<ifreund>
and pixman is quite low-level
<gbrlsnchs>
For my use case, only text (and emojis) is good enough
<bwbuhse>
Right now, on wayland, you can't screencast individual windows, right? Only the whole screen?
<gbrlsnchs>
ifreund: But out of curiosity, are bars external to rwm still compatible? Like, can they create surfaces independently and directly with the display server?
<ifreund>
gbrlsnchs: not yet as the rwm branch doesn't support wlr-layer-shell yet
<ifreund>
it is planned, but the window manager will have to opt-in to support and do a small amount of work
<ifreund>
bwbuhse: that's right, but support for sharing individual windows is getting close
<gbrlsnchs>
ifreund: I see. So right now only rendering your own bar is possible. That's good enough, I'll try something once I have a minimal version I can daily drive
<ifreund>
layer shell support is fairly high on my todo list by the way, I want to be able to run fuzzel myself :D
<gbrlsnchs>
ifreund: that would be needed for wbg as well I think, easier to run that than having to maintain code to show a background image =P
Axenntio has quit [Remote host closed the connection]
siaal has joined #river
twelve has joined #river
twelve has quit [Remote host closed the connection]
twelve has joined #river
twelve has quit [Client Quit]
siaal has quit [Remote host closed the connection]
siaal has joined #river
<gbrlsnchs>
only god knows for how long I've been using headless output and wl-mirror in order to share my screen at work, toplevel screensharing is a very welcome addition