Dusky currently has no official way to uninstall itself cleanly. Since it deploys files using a bare git repository directly into $HOME, there is no package manager or installer to reverse the process. Users who want to move on from Dusky — whether to switch configs, troubleshoot, or do a clean reinstall — are left to manually track down and delete scattered files across ~/.config, ~/.local/bin, ~/.local/share, shell rc files, and the bare repo itself.
This creates a frustrating and error-prone experience, especially for newer Arch/Hyprland users who may not know exactly what was placed where.
What I'm requesting
An official uninstall.sh script (or a dusky uninstall command if the CLI supports it) that handles:
- Removal of the
~/dusky bare git repo
- Cleanup of deployed config directories (
~/.config/hypr, ~/.config/waybar, ~/.config/rofi, ~/.config/dunst, ~/.config/matugen, etc.)
- Removal of Dusky scripts from
~/.local/bin and ~/.local/share
- Deletion of
~/.git_dusky_list
- Stripping of Dusky-related aliases/lines from
.bashrc / .zshrc
- Optional removal of packages installed by Dusky
Ideally it should be interactive — asking the user before removing each component — and should warn them to have their own Hyprland config ready before proceeding.
Why this matters
Projects like JaKooLit's Hyprland-Dots added an uninstall script and it was very well received by the community. Given how many files Dusky touches across the home directory, an official removal path would make the project feel more complete and trustworthy, especially for users who want to try it without feeling locked in.
Dusky currently has no official way to uninstall itself cleanly. Since it deploys files using a bare git repository directly into
$HOME, there is no package manager or installer to reverse the process. Users who want to move on from Dusky — whether to switch configs, troubleshoot, or do a clean reinstall — are left to manually track down and delete scattered files across~/.config,~/.local/bin,~/.local/share, shell rc files, and the bare repo itself.This creates a frustrating and error-prone experience, especially for newer Arch/Hyprland users who may not know exactly what was placed where.
What I'm requesting
An official
uninstall.shscript (or adusky uninstallcommand if the CLI supports it) that handles:~/duskybare git repo~/.config/hypr,~/.config/waybar,~/.config/rofi,~/.config/dunst,~/.config/matugen, etc.)~/.local/binand~/.local/share~/.git_dusky_list.bashrc/.zshrcIdeally it should be interactive — asking the user before removing each component — and should warn them to have their own Hyprland config ready before proceeding.
Why this matters
Projects like JaKooLit's Hyprland-Dots added an uninstall script and it was very well received by the community. Given how many files Dusky touches across the home directory, an official removal path would make the project feel more complete and trustworthy, especially for users who want to try it without feeling locked in.