rope/nixos
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

hyprland: shrink the terminal scratchpad to 60%

Browse source
This commit is contained in:
rope 2026-08-19 19:24:23 +01:00
parent 8df52a3686
commit d83b830c1c
2 changed files with 22 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

2
settings/hyprland.nix
View file

@ -397,7 +397,7 @@ in
name = "scratchpad-inset", name = "scratchpad-inset",
match = { class = "^dev.fred.scratchpad$" }, match = { class = "^dev.fred.scratchpad$" },
float = true, float = true,
size = "80% 80%", size = "60% 60%",
center = true, center = true,
}) })

34
settings/theming.nix
View file

@ -461,20 +461,12 @@ let
# GTK4 still needs it: libadwaita ignores gtk-theme-name, so user CSS is # GTK4 still needs it: libadwaita ignores gtk-theme-name, so user CSS is
# the only way in, and those apps do change only on restart. # the only way in, and those apps do change only on restart.
install -Dm644 "$theme/gtk4.css" "$HOME/.config/gtk-4.0/gtk.css" install -Dm644 "$theme/gtk4.css" "$HOME/.config/gtk-4.0/gtk.css"
# Vesktop gets the same CSS twice, on purpose. # quickCss, and ONLY quickCss. This file is a variable override layer for
# # the Midnight theme — it restates :root custom properties — so it has to
# quickCss is what applies with no setup, but vencord watches it with # be applied after Midnight to win, and vencord injects quickCss after
# fs.watch on the FILE, and in practice that watcher delivers exactly one # themes. Shipping the same CSS as a theme instead puts it in the same
# event per vesktop run here — every switch after the first is ignored # cascade slot as Midnight, where load order decides and we lose.
# until vesktop restarts. (The writes themselves are fine: a standalone
# fs.watch sees every one of these installs.)
#
# The themes directory is vencord's other watcher and it watches the
# DIRECTORY, whose inode nothing ever replaces, so it keeps firing. Enable
# "fredos" once under Vencord → Themes and switches apply live. Identical
# declarations from both sources land on the same result.
install -Dm644 "$theme/vesktop.css" "$HOME/.config/vesktop/settings/quickCss.css" install -Dm644 "$theme/vesktop.css" "$HOME/.config/vesktop/settings/quickCss.css"
install -Dm644 "$theme/vesktop.css" "$HOME/.config/vesktop/themes/fredos.css"
install -Dm644 "$theme/zen.css" "$HOME/${zenChrome}/userChrome.css" install -Dm644 "$theme/zen.css" "$HOME/${zenChrome}/userChrome.css"
# Icon theme: replace the directory contents (cheap — the tree is # Icon theme: replace the directory contents (cheap — the tree is
@ -519,6 +511,22 @@ let
fi fi
fi fi
# Vesktop: the file above is always correct, but vencord watches it with
# fs.watch on the FILE and delivers one event per vesktop run here, so
# every switch after the first is ignored. (Not our writes — a standalone
# fs.watch sees all of them.) Reloading the renderer re-runs
# VencordInitFileWatchers, which re-reads quickCss and rebinds the watch.
#
# Ctrl+R is Electron's reload accelerator, and it is the same thing that
# works by hand. Cost: discord visibly reloads for a second or two on
# every switch. Delete these three lines if that annoys more than the
# stale colours do.
if ${pkgs.hyprland}/bin/hyprctl -j clients 2>/dev/null \
| ${pkgs.jq}/bin/jq -e 'any(.[].class; test("^[Vv]esktop$"))' >/dev/null 2>&1; then
${pkgs.hyprland}/bin/hyprctl dispatch sendshortcut 'CTRL, R, class:^([Vv]esktop)$' \
|| echo "vesktop sendshortcut failed"
fi
# Point GTK3 at this wallpaper's theme. Every wallpaper has its own theme # Point GTK3 at this wallpaper's theme. Every wallpaper has its own theme
# name, so this is always a real change: gsettings emits, the portal # name, so this is always a real change: gsettings emits, the portal
# forwards it, and running GTK3 apps reload the named theme — no restart, # forwards it, and running GTK3 apps reload the named theme — no restart,