15:24 pq: emersion, swick[m], I'm back now, but it's end-of-day so tomorrow really. Is the libdisplay-info doc in place explaining what's stable and what's not? I'll try to have a look tomorrow.
16:05 mjt: how to remap keyboard keys? with X11 there were xmodmap. But with wayland?
16:05 emersion: the sway wiki has clues
16:06 mjt: it smells like sway is The wayland compositor these days :)
16:07 daniels: well, it's one of them
16:07 ManMower: there used to be a reference compositor, back in the old days.
16:07 emersion: sway users are more likely than others to want to do this
16:08 mjt: why?
16:08 emersion: thankfully, the solution only requires xkbcommon, nothing sway-specific
16:09 emersion: because it's kind of a "power user" feature kind of thing
16:10 mjt: actually I found another source of info. The manufacturer of my new keyboard included a reference for linux, including key remappingm :)
16:12 emersion: hardware accelerated key remapping
16:12 mjt: heh
16:12 mjt: some of these keyboads have hardware remapping capabilities
16:13 mjt: it's keychron k3 - this one doesn't, but there's keychron linux group on fb
17:28 mjt: ManMower: there used to be a reference compositor.. do you mean weston or sway? :)
17:29 kennylevinsen: weston
17:30 mjt: weston does exist still :)
17:31 mjt: I weren't able to use it no matter how I tried though, due to bus
17:31 mjt: bugs
17:31 kennylevinsen: yeah but its state as reference compositor is a little more complicated these days
17:32 kennylevinsen: what is a reference compositor? one implementing all protocols? only core? can it be opinionated and have real features or should it be barebones? should it be a desktop-centric compositor? etc.
17:32 daniels: mjt: oh, I thought the wlfreerdp issues were caused by your own experiments
17:34 mjt: these are bugs. pars (most) in wayland parts in wlfreerdp
17:35 mjt: I ended up switching back to ol'good Xorg in the end
17:35 daniels: ah
17:36 mjt: none of wayland stuff worked - neither with native wayland apps (wlfreerdp) nor with x11 variants of those
17:36 mjt: with weston it is most problematic. with sway it *almost* works
17:37 mjt: (sway 1.8 has some weird issues with multiple monitors)
18:29 uniqdom: Hello, I'm new trying Wayland by using Weston in X11. Is there a way to copy/paste between Weston and X11 apps?
19:56 i509VCB: Some of the Wayland protocols are inconsistent around what should happen to child objects when the global is destroyed by the client. The xdg_wm_base raises a protocol error if any child objects are alive when the destructor is called, but other protocols simply make these child objects inert or the child objects continue to be valid. This inconsistentcy is intentional or should protocols be following one of the cases?
20:59 vyivel: i509VCB: in xdg_wm_base case, destroying while at least one toplevel is alive is illegal as it's used for pinging; otherwise, it makes little sense to keep an unused object alive, so other protocol extensions allow to destroy the shell object