Saltar al contenido
GitHubGitHub (wiki)

Install / Update / Uninstall

Este contenido no está disponible en español

Make a choice between the two below, then follow the prompts.

Run the command below:

bash <(curl -s https://ii.clsty.link/get)

It clones the repo to ~/.cache/dots-hyprland by default and run ./setup install for you.

The following links are about community forks for other distros.

Distro support: basically any distro.

t=~/.cache/dots-hyprland   # Let's not trash your home folder
git clone https://github.com/end-4/dots-hyprland.git "$t" --filter=blob:none
cd "$t"

For Arch(-based) distros:

  • Install all packages listed as the value of array depends inside those ./sdata/dist-arch/*/PKGBUILD. Just use an AUR helper such as yay.
    • You may also instead install suitable alternatives as you’ve found out.

For non-Arch distros:

  • Figure out the equivalents of the packages which sdata/dist-arch/install-deps.sh installed. They are mainly from the value of array depends inside those ./sdata/dist-arch/*/PKGBUILD, and then install them.
  • To get info of a package (e.g. what executable(s) it provides), search it on Arch Linux Packages or the AUR.
  • sdata/dist-fallback/install-deps.sh also contains some installing functions for some dependencies as alternative, which are not distro-specific but out of control from the system package manager. Better avoid using them if possible.
  • If you’ve successfully finished installation on some non-Arch(-based) Linux distro, you may create an sdata/dist-<DISTRO_ID>/ directory and submit a PR. For details see this page.
    • Run ./diagnose to get the actual value of <DISTRO_ID> after distro ID:.

Read the content of sdata/dist-arch/install-setups.sh.

  • If you think it’s just fine, then just run ./setup install-setups which will run this script.
    • Do not run sdata/dist-arch/install-setups.sh directly because it’s meant to be sourced by ./setup.
  • Or, run the lines in this script manually with your tweaks.
  • Copy dots/* to your $HOME/ (review before doing this or you might have your own config files undesirably overwritten)
  • Or, read sdata/subcmd-install/3.files.sh.
    • If you think it’s just fine, then just run ./setup install-files which will run this script.
    • Do not run sdata/subcmd-install/3.files.sh directly because it’s meant to be sourced by ./setup.
  • Once you’re done, log in again into Hyprland.
    • Ctrl+Super+T to select a wallpaper.
    • Super+/ for a list of keybinds. Have fun!
  • Notification daemons like dunst and mako may come with your distro’s customizations and can interfere with Quickshell’s implementation. It is recommended to uninstall them if you don’t use them anywhere else.

See if you’re interested in anything in the dots-extra/ folder.

If you want media thumbnail from your browser to be shown, get the “Plasma browser integration” extension.

Put this line into your ~/.zshrc to support colorscheme for ZSH:

source ~/.config/zshrc.d/dots-hyprland.zsh
  • To launch Hyprland, you can use a DM (Display Manager) or just tty.
  • Hyprland wiki recommends launching Hyprland with the uswm-managed session, but we don’t. Using this does not break the dotfiles, but you might get autostarted junk from other desktop environments (for example duplicate authentication dialogs)

See Hyprland wiki for details. Below are some extra hints.

How to auto-launch Hyprland after logging in on tty1?

Section titled “How to auto-launch Hyprland after logging in on tty1?”

For ZSH or BASH, add this line to the bottom of your ~/.zshrc or ~/.bashrc:

source ~/.config/zshrc.d/auto-Hypr.sh

For FISH, add this line to the bottom of your ~/.config/fish/config.fish:

source ~/.config/fish/auto-Hypr.fish

P.S. It’s recommended to disable the DM if you want to launch Hyprland through tty.

Here’s a brief introduction to give you a quick access, though not exactly true.

You may see tty as some “basis” of a Linux system. There’re normally 7 ttys: tty1 to tty7. You may press Ctrl+Alt+F<n> to switch to tty<n>, and type your username and password to log in.

After logging in, you’re able to launch a graphical environment through command, e.g. Hyprland. Commonly, the graphical interfaces could be launched only after you login.

But what if we want a graphical interface for the login interface itself?

So, here comes the DM (Display Manager, also called “LM”, i.e. Login Manager).

  • Some commonly used DM:
    • sddm: Often used with KDE Plasma.
    • gdm: Often used with Gnome.
  • It’s enabled on system level, and launches automatically after system booting (not logging in yet).
    • On a systemd-based distro, the DM is usually enabled as a systemd service. Run the following to see which DM is enabled.
      grep 'ExecStart=' /etc/systemd/system/display-manager.service
      If it returns No such file or directory, then no DM is enabled, or this is not a systemd-based distro.
  • It provides you with a graphical interface to login and choose the graphical environment (e.g. Hyprland).
    • How does the DM know which graphical environments are available?
      • Normally, it searches the path /usr/share/xsessions for X11 ones, and /usr/share/wayland-sessions for Wayland ones.
      • The desktop files under these directories contain the information of the graphical environments.
  • cd into the repo directory
  • Run git pull to fetch the latest changes.
  • Run ./setup install again
    • Skip the steps you don’t want (especially the rsync ... ones because it will override your files under its target path). Typically you may want the rsync step which involves dots/.config/quickshell.
  • You can try using ./setup exp-uninstall, but it’s not perfect and not actively maintained.
  • Manual uninstallation hint for Arch Linux:
    • Run pacman -Q | grep illogical-impulse for a list of packages the dotfiles requires.
    • Run yay -Rs PACKAGE_NAME for each package from the above command.