commit: 7cc087037de9f4ebc3de71115695f0f8256891ed
parent b8d74ef4e55de97f1e6e62a87d3c82c0f1fe1aea
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Mon, 8 Mar 2021 02:55:00 +0000
articles/Why I embraced Wayland: Rephrase input device settings on Xorg for clarity
Diffstat:
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/articles/Why I embraced Wayland.xhtml b/articles/Why I embraced Wayland.xhtml
@@ -9,7 +9,7 @@
<ul>
<li>applications like Firefox shitting all over the desktop at times, leaving ghosted areas;</li>
<li>all applications being able to send any and receive all keyboard+mouse input with no real solution against that (I know XTerm has some option to steal all keyboard input, didn't work for me);</li>
- <li>keyboard layout/mapping tools (<code>setxkbmap(1)</code>, <code>xmodmap(1)</code>, …) being done done for a logic where you have one keyboard (as each can have their own layout) and no hotplugging (because it gets set to <code>Xorg.conf</code> or defaults on plugging it);</li>
+ <li>non-orthogonality of input device settings; XOrg allows to have a different settings on each and would require managing hotplug events but XOrg tools (<code>setxkbmap(1)</code>, <code>xmodmap(1)</code>, …) are done for a display server that would support only one layout setting and manage events by itself</li>
<li>display configuration hell, I know how to use <code>xrandr(1)</code> for some arcane things now (including trashing the concept of VTs, thanks linux) but what a mess and of course no support for hotplugging (which is a mess unless you use a tiling window manager like XMonad);</li>
<li>normal applications being able to trash your setup (ie. multi-monitor to a single display at 640x480) and no restoring if they crash down or don't care;</li>
<li>applications often behaving weirdly when a tiling window manager resizes them automatically;</li>
@@ -49,5 +49,5 @@
</ol>
<p>And yeah a lot of that list is linked to wlroots, feel free to pass on links from others, I know MATE is planning to switch to Wayland but it's still mostly for the future and I don't know how well wayland works in KDE (hopefully quite well).</p>
<p>Note: I usually read replies to my articles but I'm not going to bother if you're going to just throw the typical clueless wayland-hater bile one can see on internet. I will probably answer honest questions though. Hopefully that will save some people's energy and time.</p>
-<p><a href="https://queer.hacktivis.me/objects/db4f70f5-7186-43ce-a350-e0e8d332bfb9">Fediverse post for comments</a>, published on 2021-03-07T00:35:00Z, last updated on 2021-03-07T00:56:00Z</p>
+<p><a href="https://queer.hacktivis.me/objects/db4f70f5-7186-43ce-a350-e0e8d332bfb9">Fediverse post for comments</a>, published on 2021-03-07T00:35:00Z, last updated on 2021-03-08T02:55:00Z</p>
</article>
diff --git a/feed.atom b/feed.atom
@@ -15,7 +15,7 @@
<link rel="alternate" type="text/html" href="/articles/Why%20I%20embraced%20Wayland"/>
<id>https://hacktivis.me/articles/Why%20I%20embraced%20Wayland</id>
<published>2021-03-07T00:35:00Z</published>
- <updated>2021-03-07T00:35:00Z</updated>
+ <updated>2021-03-08T02:55:00Z</updated>
<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<!--#include file="/articles/Why I embraced Wayland.xhtml"-->
</div></content>
