oat
/
nix-config
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

bitwarden password keybind. you technically need to `rbw login` but oh well

This commit is contained in:
Jill 2024-01-04 21:25:35 +03:00
parent ec7950ee39
commit 63d12637d9
1 changed files with 18 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
home-manager/home.nix
View File

@ -1,4 +1,4 @@
{ inputs, outputs, pkgs, ... }:
{ inputs, outputs, pkgs, lib, ... }:
{
imports = [
@ -38,7 +38,7 @@
# misc
cowsay file which tree gnused grc
# um
doas-sudo-shim gnome.dconf-editor
doas-sudo-shim gnome.dconf-editor rbw
];
colorScheme = inputs.nix-colors.colorSchemes.catppuccin-mocha;
@ -130,17 +130,31 @@
"show-screenshot-ui" = [];
};
gnomeBindings.wm = {
"panel-run-dialog" = [ "Launch1" ];
#"panel-run-dialog" = [ "Launch1" ];
};
gnomeBindings.custom = {
"take-screenshot" = {
binding = "Print";
command = "${pkgs.lib.getExe pkgs.flameshot} gui";
command = "${lib.getExe pkgs.flameshot} gui";
};
"grab-password" = let
grabScript = pkgs.writeScript "grab-password" ''
${lib.getExe pkgs.rbw} get $(${lib.getExe pkgs.gnome.zenity} --entry --text="" --title="") | ${lib.getExe pkgs.xclip} -selection clipboard
'';
in {
binding = "Launch1";
command = ''${grabScript}'';
};
};
# usually you don't need to do this, but this is a workaround for https://github.com/flameshot-org/flameshot/issues/3328
services.flameshot.enable = true;
programs.rbw = {
enable = true;
settings.base_url = "https://bitwarden.lavatech.top";
settings.email = "oatmealine@disroot.org";
};
# This value determines the home Manager release that your
# configuration is compatible with. This helps avoid breakage
# when a new home Manager release introduces backwards