Compare commits

..

No commits in common. "nix/home" and "master" have entirely different histories.

10 changed files with 19 additions and 87 deletions

2
dwl

@ -1 +1 @@
Subproject commit e3f8b3e1db2efb21d4ca4786e86adda09d870aa9
Subproject commit 01082b4d9e1a927e186a2e8cdb4c606f66b03ffd

View file

@ -1,77 +0,0 @@
{ config, pkgs, ... }:
{
# Home Manager needs a bit of information about you and the paths it should
# manage.
home.username = "steven";
home.homeDirectory = "/home/steven";
# 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 incompatible changes.
#
# You should not change this value, even if you update Home Manager. If you do
# want to update the value, then make sure to first check the Home Manager
# release notes.
home.stateVersion = "25.11"; # Please read the comment before changing.
# The home.packages option allows you to install Nix packages into your
# environment.
home.packages = [
# # Adds the 'hello' command to your environment. It prints a friendly
# # "Hello, world!" when run.
# pkgs.hello
# # It is sometimes useful to fine-tune packages, for example, by applying
# # overrides. You can do that directly here, just don't forget the
# # parentheses. Maybe you want to install Nerd Fonts with a limited number of
# # fonts?
# (pkgs.nerdfonts.override { fonts = [ "FantasqueSansMono" ]; })
# # You can also create simple shell scripts directly inside your
# # configuration. For example, this adds a command 'my-hello' to your
# # environment:
# (pkgs.writeShellScriptBin "my-hello" ''
# echo "Hello, ${config.home.username}!"
# '')
import ./scripts
];
# Home Manager is pretty good at managing dotfiles. The primary way to manage
# plain files is through 'home.file'.
home.file = {
# # Building this configuration will create a copy of 'dotfiles/screenrc' in
# # the Nix store. Activating the configuration will then make '~/.screenrc' a
# # symlink to the Nix store copy.
# ".screenrc".source = dotfiles/screenrc;
# # You can also set the file content immediately.
# ".gradle/gradle.properties".text = ''
# org.gradle.console=verbose
# org.gradle.daemon.idletimeout=3600000
# '';
};
# Home Manager can also manage your environment variables through
# 'home.sessionVariables'. These will be explicitly sourced when using a
# shell provided by Home Manager. If you don't want to manage your shell
# through Home Manager then you have to manually source 'hm-session-vars.sh'
# located at either
#
# ~/.nix-profile/etc/profile.d/hm-session-vars.sh
#
# or
#
# ~/.local/state/nix/profiles/profile/etc/profile.d/hm-session-vars.sh
#
# or
#
# /etc/profiles/per-user/steven/etc/profile.d/hm-session-vars.sh
#
home.sessionVariables = {
# EDITOR = "emacs";
};
# Let Home Manager install and manage itself.
programs.home-manager.enable = true;
}

View file

@ -1,7 +0,0 @@
{
pkgs,
}: [
(pkgs.writeShellApplication {
name = "vol.sh";
}
]

17
scripts/Makefile Normal file
View file

@ -0,0 +1,17 @@
SHELL := /bin/bash
DEST := /usr/local/bin
SRC := ./src/
install:
@if [ "$$(id -u)" -ne 0 ]; then \
echo "Error: You must be root to run 'make install'."; \
exit 1; \
fi
@find $(SRC) -type f | while IFS= read -r fpath; do \
filename="$${fpath##*/}"; \
echo "Installing $$filename ..."; \
install -m 755 "$$fpath" "$(DEST)/$$filename"; \
done

View file

@ -1,4 +1,3 @@
#!/usr/bin/bash
#!/usr/bin/sh
systemctl --user import-environment WAYLAND_DISPLAY
. "$HOME/.nix-profile/etc/profile.d/hm-session-vars.sh"
swaybg -i $HOME/wallpaper.jpg