s1341_ has quit [Quit: Connection closed for inactivity]
mcornick has quit [Quit: leaving]
mcornick has joined #home-manager
mcornick has quit [Quit: zzz]
cole-h_ has joined #home-manager
cole-h_ is now known as cole-h
srk has quit [Remote host closed the connection]
srk has joined #home-manager
cole-h has quit [Ping timeout: 264 seconds]
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #home-manager
__monty__ has joined #home-manager
benkolera has quit [Quit: Connection closed for inactivity]
Synthetica has joined #home-manager
jv7 has joined #home-manager
<jv7>
I've tried to declare a service to run but bumped up against this 'User systemd daemon not running. Skipping reload.' Is there something I need to do to get systemd to run for my user?
<jv7>
systemctl --user gives me failed to connect to bus operation not permitted. Thinking that is related but unsure how to resolve.
<lunik1>
are you on nixos?
s1341_ has joined #home-manager
<jv7>
@lunk1 yes I am
<jv7>
I think I understand, the systemd user daemon will only load on user login, I was `su` to switch to the user rather than logging in.
cole-h has joined #home-manager
jv7 has quit [Quit: Connection closed]
zetashift has joined #home-manager
<zetashift>
Hiya all! When I remove a package in my `home.nix` for example `emacs` and run `home-manager switch` the emacs command is still available and the package is not removed, is there anyway to force this? The same goes for when I want to install `lorri` by adding it to my `home.packages` but it's not being installed
<SumnerEvans[m]>
Is it installed globally? What does `which emacs` show?
appservicebot13 has quit [Quit: killed]
piegames[m] has quit [Quit: killed]
piegames[m] has joined #home-manager
appservicebot11 has joined #home-manager
<zetashift>
`which emacs` shows me `/home/rishi/.nix-profile/bin/emacs`
<zetashift>
The same happens for other stuff like `starship`
rajivr has quit [Quit: Connection closed for inactivity]
<zetashift>
Also if I for example remove `emacs` or `starship` there is no new generation added?
<zetashift>
I'm a beginner to Nix so I don't know that much, I could find anything about why home-manager doesn't remove it, should I just uninstall home-manager and reinstall it?
<rycee>
zetashift: Try `nix-env -q` and see if you have them listed there.
<zetashift>
I don't
<zetashift>
```any-nix-shell-1.2.1
<zetashift>
cachix-0.6.0
<zetashift>
home-manager-path
<zetashift>
nix-2.3.10
<zetashift>
nixGLCommon ```
<zetashift>
whoops my bad
<rycee>
zetashift: Do you have `programs.emacs.enable` in your configuration?
<zetashift>
And my current `home-manager packages` even after running home-manager switch against my current config: https://dpaste.com/3HSW738TJ
<zetashift>
It's not only emacs that does not get deleted, the same goes for starship or ripgrep, I am runninng a sinngle user install
<rycee>
zetashift: Hmm, try doing a switch with the configuration file given explicitly: Something like `home-manager -f ~/.config/nixpkgs/home.nix switch`.
<zetashift>
Still doesn't change anything :(
<rycee>
zetashift: Is `~/.config/nixpkgs/home.nix` an actual file or a link elsewhere?
<rycee>
Specifically, if you do `cat ~/.config/nixpkgs/home.nix`, do you actually get the code in the dpaste link?
<rycee>
Alternatively, if you run with `home-manager -v switch`, do you get all three lines `Activating installPackages`, `replacing old 'home-manager-path'`, and `installing 'home-manager-path'`?
<zetashift>
@rycee `cat home.nix` indeed returns the code from the dpaste link, but `home-manager -v switch` does not show the three lines, it shows: `/nix/store/5vljqx9nlbif545zxhqlb2kh3bff3b08-home-manager-generation
<zetashift>
tput: unknown terminal "xterm-kitty"`
<zetashift>
I ran it in gnome terminal and it worked ><
<zetashift>
Sorry for the nooby question thanks for helping me :D
<rycee>
No worried. Quite curious, though. that a erroring tput would cause such a problem.
<zetashift>
I had that error on all the `home-manager switch` runs, but I thought even if it couldn't get the terminal it would still do it in the background I guess, cause the initial install worked fine