ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
c7s has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
leon-p has quit [Quit: leon-p]
Seirdy has quit [Ping timeout: 480 seconds]
Seirdy has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
dcz_ has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]
Doraemon has joined #wayland
NeoCron has quit [Ping timeout: 480 seconds]
agd5f has quit [Ping timeout: 480 seconds]
hardening has joined #wayland
danvet has joined #wayland
d42 has quit [Ping timeout: 480 seconds]
<pq>
Shimmy, I think generally there are no "good for newcomers" tasks in xserver by definition. Everything is going to be a pain even after you know how Wayland *and* X11 protocols are supposed to work.
<emersion>
we should have a "good for people ready to walk into the depths of hell" label
<wb9688>
haha
dcz_ has joined #wayland
<Shimmy>
That's uplifting 😆
leon-p has joined #wayland
flacks has quit [Quit: Quitter]
flacks has joined #wayland
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #wayland
jgrulich has joined #wayland
c7s has joined #wayland
ryoshu has quit [Ping timeout: 480 seconds]
arinov has joined #wayland
<arinov>
hi
<arinov>
i am moving from X11 to wayland
rasterman has joined #wayland
<arinov>
switching my wm backend to wayland i lost keyboard layout switching and selection buffer
<arinov>
with both i believe was X11 features
<arinov>
how to switch layouts novadays in wm?
<arinov>
i had localectl from systemd configured before, and seems it sets X11 env vars only
<wb9688>
arinov: What compositor are you using?
leon-p has quit [Remote host closed the connection]
<arinov>
wb9688: dont know exactly, how to find out? qtile wm seems has something inside
boistordu has joined #wayland
arinov has quit [Quit: WeeChat 3.3]
c7s has quit [Quit: c7s]
leon-p has joined #wayland
cvmn has joined #wayland
jgrulich has quit [Remote host closed the connection]
c7s has joined #wayland
cvmn has quit [Quit: see ya l8tr (i.a.)]
d42 has joined #wayland
zebrag has joined #wayland
rawoul has quit [Quit: leaving]
d_ed has joined #wayland
novakane has joined #wayland
d_ed has quit [Remote host closed the connection]
feiqu has joined #wayland
vyivel has quit [Remote host closed the connection]
bl4ckb0ne has quit [Remote host closed the connection]
emersion has quit [Remote host closed the connection]
bl4ckb0ne has joined #wayland
vyivel has joined #wayland
emersion has joined #wayland
c7s has quit [Quit: c7s]
c7s has joined #wayland
c7s has quit [Quit: c7s]
c7s has joined #wayland
c7s has quit []
c7s has joined #wayland
feiqu has quit [Quit: feiqu]
novakane has quit [Quit: WeeChat 3.3]
<wb9688>
zzag[m] and romangg: I noticed that KDE and wlroots both have Wayland protocols that serve the same purpose, e.g. for output management. I was talking with ammen99[m] about that and I am wondering if we could agree on a single protocol in such cases.
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
Doraemon has quit []
NeoCron has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
danvet has quit [Ping timeout: 480 seconds]
dcz_ has joined #wayland
hardening has quit [Ping timeout: 480 seconds]
Seirdy has quit []
Seirdy has joined #wayland
<romangg>
wb9688: I would love to have a single one for sure. The wlroots one is better in terms of protocol hygiene. I'm not sure how the custom mode thing of the protocol is to be implented though and what it's usecase is.