<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DankMaterialShell on Elis Hirwing</title><link>https://elis.nu/tags/dankmaterialshell/</link><description>Recent content in DankMaterialShell on Elis Hirwing</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 08 Sep 2026 23:00:00 +0200</lastBuildDate><atom:link href="https://elis.nu/tags/dankmaterialshell/index.xml" rel="self" type="application/rss+xml"/><item><title>Simplifying my Sway setup with DankMaterialShell</title><link>https://elis.nu/blog/2026/09/simplifying-sway-with-dankmaterialshell/</link><pubDate>Tue, 08 Sep 2026 23:00:00 +0200</pubDate><guid>https://elis.nu/blog/2026/09/simplifying-sway-with-dankmaterialshell/</guid><description>&lt;p&gt;Over the years my &lt;a href="https://swaywm.org/"&gt;Sway&lt;/a&gt; setup had grown into a pile of&#10;independently configured single-purpose tools: a bar, a launcher that also&#10;doubled as an emoji picker and power menu, a notification daemon, a lock&#10;screen plus idle daemon, a media-key/Bluetooth setup glued together with a&#10;few standalone helpers, and a separate screenshot tool. Each one worked, but&#10;each one was its own little island with its own config format and its own&#10;opinions about how to talk to the others.&lt;/p&gt;</description></item></channel></rss>