From ed615c754788c4bedc19f46f9e7e1f74c12cd260 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 May 2026 12:53:02 -0500 Subject: chore(hyprland): capture pypr output to a per-session log file Pypr was sending stderr to /dev/null. So when its keybind clients emitted red `hyprctl notify` banners after the daemon got stuck, there was no trace to read. I followed the waybar / dunst / hypridle / gammastep pattern already in the same exec-once block. --- dotfiles/hyprland/.config/hypr/hyprland.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'dotfiles') diff --git a/dotfiles/hyprland/.config/hypr/hyprland.conf b/dotfiles/hyprland/.config/hypr/hyprland.conf index 4850e87..230b42a 100644 --- a/dotfiles/hyprland/.config/hypr/hyprland.conf +++ b/dotfiles/hyprland/.config/hypr/hyprland.conf @@ -36,7 +36,7 @@ exec-once = mpd exec-once = pocketbook --hidden # Pyprland (scratchpads, magnify, etc.) -exec-once = pypr +exec-once = pypr > ~/.local/var/log/pypr-$(date +%Y-%m-%d-%H%M%S).log 2>&1 exec-once = hypr-refocus-scratchpad # Apps that can start later (sleep ensures waybar tray is registered) -- cgit v1.2.3