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
ManMower has quit []
Lyude has quit [Server closed connection]
Lyude has joined #wayland
ManMower has joined #wayland
maxzor__ has quit [Ping timeout: 480 seconds]
maxzor_ has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
evx256 has quit [Server closed connection]
evx256 has joined #wayland
rv1sr has quit []
maxzor_ has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
maxzor_ has quit [Remote host closed the connection]
maxzor_ has joined #wayland
maxzor__ has joined #wayland
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #wayland
ahartmetz has quit [Quit: Konversation terminated!]
maxzor__ has quit [Ping timeout: 480 seconds]
JPEW has quit [Server closed connection]
JPEW has joined #wayland
Emet-Selch has joined #wayland
erc_ has joined #wayland
Azem has quit [Ping timeout: 480 seconds]
erc has quit [Ping timeout: 480 seconds]
txtsd has quit [Ping timeout: 480 seconds]
melissawen has quit [Server closed connection]
melissawen has joined #wayland
tdeo has quit [Server closed connection]
tdeo has joined #wayland
jmdaemon has joined #wayland
Company has quit [Read error: Connection reset by peer]
Seirdy has quit [Server closed connection]
Seirdy has joined #wayland
maxzor__ has joined #wayland
maxzor has joined #wayland
maxzor__ has quit [Ping timeout: 480 seconds]
eroux has joined #wayland
danvet has joined #wayland
jgrulich has joined #wayland
DonRichie has joined #wayland
zebrag has quit [Remote host closed the connection]
shankaru has joined #wayland
hardening has joined #wayland
evon377 has quit [Ping timeout: 480 seconds]
pnowack has joined #wayland
c7s has joined #wayland
rgallaispou has joined #wayland
DebianUserMaybe has joined #wayland
duxsco has joined #wayland
manuel1985 has joined #wayland
mvlad has joined #wayland
jmdaemon has quit [Quit: WeeChat 3.4]
jmdaemon has joined #wayland
kenny has quit []
MajorBiscuit has joined #wayland
dcz_ has joined #wayland
jmdaemon has quit [Quit: WeeChat 3.4]
jmdaemon has joined #wayland
txtsd has joined #wayland
rasterman has joined #wayland
l4s8g has joined #wayland
sillyslux has quit [Read error: Connection reset by peer]
rv1sr has joined #wayland
pounce has quit [Ping timeout: 480 seconds]
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
txtsd has quit [Quit: WeeChat 3.4]
txtsd has joined #wayland
fmuellner has joined #wayland
pounce has joined #wayland
sillyslux has joined #wayland
sillyslux has quit [Read error: Connection reset by peer]
jmdaemon has quit [Ping timeout: 480 seconds]
duxsco has quit [Quit: duxsco]
devilhorns has joined #wayland
eroux_ has joined #wayland
eroux has quit [Ping timeout: 480 seconds]
masoudd_ has quit [Ping timeout: 480 seconds]
ahartmetz has joined #wayland
cabal704 has joined #wayland
tanty has quit []
DebianUserMaybe has quit [Remote host closed the connection]
DebianUserMaybe has joined #wayland
sillyslux has joined #wayland
tanty has joined #wayland
rgallaispou has quit [Read error: Connection reset by peer]
sillyslux has quit [Read error: Connection reset by peer]
rv1sr has quit []
<wlb> wayland Merge request !214 opened by () connection: Read more data per call to wl_connection_read() https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/214
Company has joined #wayland
cabal704 has quit [Ping timeout: 480 seconds]
maxzor has quit [Ping timeout: 480 seconds]
cvmn has joined #wayland
maxzor has joined #wayland
quentin123 has joined #wayland
masoudd_ has joined #wayland
cvmn has quit [Remote host closed the connection]
cabal704 has joined #wayland
pnowack has quit [Quit: pnowack]
cabal704 has quit [Quit: WeeChat 3.4]
spstarr has joined #wayland
pnowack has joined #wayland
pnowack has quit [Remote host closed the connection]
pnowack has joined #wayland
eroux_ has quit [Read error: Connection reset by peer]
eroux has joined #wayland
rv1sr has joined #wayland
manuel1985 has quit []
rgallaispou has joined #wayland
rv1sr has quit []
rgallaispou has quit [Read error: Connection reset by peer]
captainchris has joined #wayland
<captainchris> Hi everybody. I have a problem using dwl under alpine . I build wayland-1.20 with wayland-protocols-1.25 wlroots-0.16. I built dwl-0.2.2, the building if fine, I can run it but when I launch application it says err:wayland.c:1225:no sub compositor
<kennylevinsen> captainchris: 0.16 is wlroots master. your version of dwl is too old for that.
<captainchris> kennylevinsen: with version 0.14.1 provided on alpine linux I have the same problem
<captainchris> I try to build 0.16 to saw if the problem persists
MajorBiscuit has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
<wlb> wayland Issue #279 opened by () (Qemu) Window resize does not repaint desktop https://gitlab.freedesktop.org/wayland/wayland/-/issues/279
<kennylevinsen> Use whatever dwl release says it depends on. The error is because later wlroots versions made a step manual.
<wlb> wayland Issue #279 closed \o/ ((Qemu) Window resize does not repaint desktop https://gitlab.freedesktop.org/wayland/wayland/-/issues/279)
devilhorns has quit []
quentin123 has quit [Remote host closed the connection]
Arnavion has quit [Remote host closed the connection]
Arnavion has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
maxzor_ has quit [Ping timeout: 480 seconds]
<bl4ckb0ne> captainchris: alpine 3.15 or edge? iirc wlroots 0.15.1 is only in edge
maxzor has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
duxsco has joined #wayland
rv1sr has joined #wayland
zebrag has joined #wayland
cabal704 has joined #wayland
<captainchris> bl4ckb0ne: alpine 3.15
<captainchris> I will try to modify dwl to adapt with wlroot-0.16
captainchris has quit [Quit: Lost terminal]
maxzor has quit [Ping timeout: 480 seconds]
cabal704 has quit [Quit: WeeChat 3.4]
shankaru has quit [Quit: Leaving.]
jmdaemon has joined #wayland
pnowack has quit [Quit: pnowack]
pnowack has joined #wayland
pnowack has quit [Remote host closed the connection]
pnowack has joined #wayland
Emet-Selch has quit [Ping timeout: 480 seconds]
masoudd_ has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
nsneck has quit [Quit: bye]
nsneck has joined #wayland
fmuellner has joined #wayland
creich_ has quit []
creich has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
danvet has quit [Ping timeout: 480 seconds]
sych1ll has quit [Ping timeout: 480 seconds]
duxsco has quit [Quit: duxsco]
sychill has joined #wayland
fmil has joined #wayland
<fmil> hi folks! I'm curious to learn a bit about the current state and the direction of keyboard input support in Wayland. Can I ask here, or should I turn to the mailing list, or something els
l4s8g has quit []
<emersion> yea feel free to ask here
mcf has quit [Ping timeout: 480 seconds]
cvmn has joined #wayland
mcf has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
DebianUserMaybe has quit []
<fmil> I noticed that Wayland delegates the implementation of key mapping to clients. How does wayland then ensure consistent handling of keymaps and autorepeat across toolkits / apps?
<fmil> it seems that delegating this responsibility would lead to inconsistent handling in different toolkits.
<fmil> What am I missing
spstarr has quit [Remote host closed the connection]
jmdaemon has joined #wayland
<fmil> And, what is the reason wayland would not handle keymapping for all clients?
hardening has quit [Ping timeout: 480 seconds]
<Sachiel> isn't it handled by the compositor?
<fmil> sachiel@ not that I can see
<fmil> IIUC the keyboard APIs are as shown here: https://wayland-book.com/seat/keyboard.html
<fmil> input events seem to be thin shims over evdev, transacting in scancodes.
<fmil> and there is an API to pass the keymap to the client to let the client figure it out.
<fmil> which leads me to wonder how desktop environments like KDE would use centralized keymap settings
<fmil> Sorry for asking trivial questions, I'm trying to learn as much as I can about what the current thinking here is.
<Sachiel> oh, huh, I remember less than I thought
<Sachiel> centralized keymaps, unless I misunderstand the question, seem to be answered in that very same link. The compositor is configured with them and it will send the keymap to each client whenever it changes, no? At least on sway I don't seem to have to configure that in more than just sway's own settings
duxsco has joined #wayland
<Sachiel> key repeat I assume it's done that way to avoid the old x11 problem of figuring out where the events you are getting are actual events or just the repeat events
jmdaemon has quit [Ping timeout: 480 seconds]
<fmil> so yes, the compositor will send keymaps indeed.
<fmil> but - it's up to each client to know what to do with it
<fmil> it being the sequence of keymaps.
AJC_Z0 has joined #wayland
AJ_Z0 has quit [Remote host closed the connection]
AJC_Z0 is now known as AJ_Z0
jmdaemon has joined #wayland
mvlad has quit [Remote host closed the connection]
AJC_Z0 has joined #wayland
<fmil> If y'all are confused on where I'm coming from, here's a bit of background.
<fmil> so I'm working on a new OS, called Fuchsia
<fmil> specifically on keyboard support.
<fmil> and am wondering how I could reuse Fuchsia's existing keyboard support in wayland apps.
<fmil> keymap processing is exactly on the "wrong" side of the wayland API for my purpose, and I was wondering how to reconcile the approaches
<fmil> Fuchsia has no notion of keymap files - at least not yet anyways, nor would they necessarily be xkb compatible even if they existed.
<fmil> so one basic question would be whether there even is a place in Wayland for delivering already keymapped key event
<fmil> and if the answer is yes, then how would one go about making it happen.
<fmil> Advice appreciated, and/or pointers to people who'd know more.
AJ_Z0 has quit [Ping timeout: 480 seconds]
AJC_Z0 is now known as AJ_Z0
<daniels> fmil: the short answer is that if you want to make shortcuts or hotkeys work, you fundamentally need keycode + modifiers + map