00:04
mtm has quit [Ping timeout: 252 seconds]
00:06
mtm has joined #river
01:27
Snetry has quit [Ping timeout: 248 seconds]
01:27
sentry has joined #river
02:15
eShaev9z_ has joined #river
02:15
eShaev9z has quit [Ping timeout: 252 seconds]
02:26
adamcstephens has quit [Remote host closed the connection]
02:27
adamcstephens has joined #river
02:34
vimproved has quit [Ping timeout: 248 seconds]
02:43
Palanix_ has joined #river
02:44
Palanix has quit [Ping timeout: 260 seconds]
02:44
Palanix_ is now known as Palanix
03:14
vimproved has joined #river
05:44
haliucinas has quit [Quit: .]
05:45
haliucinas has joined #river
06:24
leopoldek has quit [Remote host closed the connection]
07:47
<
__toor__ >
does waybar require d-bus? I had no idea.. too bad. So, what can you recommend to use instead of waybar?
07:48
<
LarstiQ >
what are your requirements? I use yambar
07:51
<
__toor__ >
yambar, let me look into that. I'd prefer to have something that doesnt require a lot of customization to get decent looking
07:55
<
__toor__ >
1) won't start without a config. 2) why not provide a default yambar.conf? makes no sense.
08:32
catman has quit [Read error: Connection reset by peer]
08:32
catman has joined #river
08:55
<
leon-p >
yambar runs on a lot of different desktops which require different modules, so a default config wouldn't work on a lot of them
08:56
<
leon-p >
but if you only care about active tags, there is also my river-tag-overlay, which will run with no configuration
08:57
<
ifreund >
there are other bars listed on the river wiki as well
09:19
<
__toor__ >
sorry, I just have customization and configuration fatigue packaging up all of these things needed to start an OS that is almost usable :D
09:19
<
__toor__ >
If I knew how much work it would be I never would have started this work lol
09:37
<
leon-p >
then welcome to the bar-less life I suppose :)
09:42
<
LarstiQ >
the joy of linux from scratch :)
09:51
<
ninewise >
nobar best bar
09:59
<
__toor__ >
mm, you might be right ;-)
10:00
<
__toor__ >
but I kind of got used to seeing the time there, and how much free memory I have is kinda useful too
10:10
<
ninewise >
The time is displayed in my IRC client so that's always visible
10:40
Den4ikRus has joined #river
12:02
mtm has quit [Ping timeout: 260 seconds]
12:05
mtm has joined #river
12:28
audubon has joined #river
12:35
audubon has quit [Ping timeout: 256 seconds]
12:54
<
lordmzte >
Is it possible to make river blur the backgrounds of semi-transparent windows/is this planned?
12:57
<
ifreund >
lordmzte: I'm not opposed to supporting that in some way in theory, but it's not going to happen anytime in the near future
13:08
Palanix has quit [Ping timeout: 246 seconds]
13:22
leopoldek has joined #river
13:25
Palanix has joined #river
15:35
Joikor has joined #river
16:11
leopoldek has quit [Remote host closed the connection]
16:14
Joikor has quit [Quit: Client closed]
17:10
lordmzte has joined #river
17:15
lordmzte has quit [Ping timeout: 252 seconds]
17:32
lordmzte has joined #river
18:13
lordmzte has joined #river
18:40
catman has quit [Quit: WeeChat 4.3.0-dev]
19:10
leopoldek has joined #river
19:32
WilhelmVonWeiner has joined #river
19:32
<
WilhelmVonWeiner >
Is there a way to make focus follow a window's change to another output?
20:03
catman has joined #river
21:24
graves1 has quit [Read error: Connection reset by peer]
21:30
graves1 has joined #river
21:38
<
leon-p >
lordmzte: ifreund: there is a MR for wayland-protocols for a blur protocol. I assume if that makes it through, blur could be handled entirely inside wlroots without us knowing anything about it
22:01
notzmv has joined #river
22:06
notzmv has quit [Ping timeout: 265 seconds]
23:19
lordmzte has quit [Ping timeout: 246 seconds]
23:27
lordmzte has joined #river