[Fix] cleanup

2026-08-13 01:11:41 +02:00
parent f62cb40499
commit 86726cddce
312 changed files with 12274 additions and 10772 deletions
@@ -0,0 +1,43 @@
+
+# █░█ █▀ █▀▀ █▀█   █▀█ █▀█ █▀▀ █▀▀ █▀
+# █▄█ ▄█ ██▄ █▀▄   █▀▀ █▀▄ ██▄ █▀░ ▄█
+
+# Set your personal hyprland configuration here
+
+
+# BAR BLUR
+#
+# The blur behind the bars only ever came from HyDE's *generated* `hypr/themes/theme.conf`,
+# which this repo deliberately does not carry (HyDE writes it per host) — so without this
+# block the bars have no blur behind them. That generated file also still ships the pre-0.45
+# form (`layerrule = blur,waybar`), which current hyprland rejects; HyDE wraps the source in
+# `hyprlang noerror true`, so it fails silently either way. Re-declared here in the current
+# `<rule>,match:namespace <ns>` syntax, matching windowrules.conf. `layerrule` is additive.
+# Keep comments on their own lines: a trailing one is parsed as part of the value.
+# (`cavabar` is the standalone cava bar from waybar/layouts/custom.jsonc.)
+layerrule = blur true,match:namespace waybar
+layerrule = ignore_alpha 0,match:namespace waybar
+layerrule = blur true,match:namespace cavabar
+layerrule = ignore_alpha 0,match:namespace cavabar
+
+
+
+# // █░░ ▄▀█ █░█ █▄░█ █▀▀ █░█
+# // █▄▄ █▀█ █▄█ █░▀█ █▄▄ █▀█
+
+# (xremap lives in lw's host.conf — it's the only host with an xremap config; wm uses evremap)
+env = SSH_AUTH_SOCK,$XDG_RUNTIME_DIR/ssh-agent.socket # ssh on start
+env = ELECTRON_OZONE_PLATFORM_HINT,x11 # Disable after hyprland fixes electron flickering
+exec-once = waybar -c ~/.config/waybar/layouts/custom.jsonc -s ~/.config/waybar/layouts/custom.css
+
+# (No static `noanim` layerrule: current Hyprland rejects it in the match: syntax, and
+#  grimblast already suppresses selection animation at runtime via `hyprctl keyword layerrule`.)
+
+
+# I know there is like two 'solutions' already, so have third one - (tested GTX 1060, 555.58.02 drivers) - run flickery apps with --disable-gpu-compositing. This makes apps slightly less smooth (GPU still used tho), but fixes the issue. I think this is better then to disable damage_tracking, which works too.
+
+# render {
+#     explicit_sync = 1
+#     explicit_sync_kms = 1
+#     direct_scanout = no
+# }