titaniumtown/nixos
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ghostty: fix???
All checks were successful
Build and Deploy / mreow (push) Successful in 1m20s
Details
Build and Deploy / yarn (push) Successful in 54s
Details
Build and Deploy / muffin (push) Successful in 1m14s
Details

Browse Source
This commit is contained in:
Simon Gardling
2026-04-26 01:11:09 -04:00
parent 4b173ef164
commit 141754ca39
2 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
home/progs/ghostty.nix
View File

@@ -55,6 +55,13 @@
# cursor # cursor
cursor-style = "underline"; cursor-style = "underline";
# always open new windows at $HOME instead of inheriting whatever cwd the
# currently-focused ghostty window has. with gtk-single-instance, the
# focused-window inherit rule otherwise sticks the daemon's first cwd to
# every subsequent niri Mod+T launch.
window-inherit-working-directory = false;
working-directory = "home";
# keep one daemon alive so subsequent launches (e.g. niri Mod+T) are # keep one daemon alive so subsequent launches (e.g. niri Mod+T) are
# instant instead of paying GTK + wgpu init each time. relies on the # instant instead of paying GTK + wgpu init each time. relies on the
# dbus-activated systemd user service that the HM module wires up. # dbus-activated systemd user service that the HM module wires up.

8
home/progs/niri.nix
View File

@@ -115,12 +115,8 @@ in
"Mod+O".action = toggle-overview; "Mod+O".action = toggle-overview;
# open a terminal — pass --working-directory=home so the gtk-single-instance # open a terminal
# daemon doesn't keep handing back whatever cwd the focused window has. "Mod+T".action = spawn config.home.sessionVariables.TERMINAL;
"Mod+T".action = spawn [
config.home.sessionVariables.TERMINAL
"--working-directory=home"
];
# lock the screen # lock the screen
"Mod+X".action = spawn (lib.getExe pkgs.swaylock); "Mod+X".action = spawn (lib.getExe pkgs.swaylock);