Hello, I have a weird problem. Since the last rebuild, helix (text editor in terminal like vim) ask me to be sudo every time no matter what file I try to edit, even without opening a file but simply by starting in a blank buffer. What could cause this ? I can’t find a moment where I hadn’t this issue even in previous build. If I checkout an old commit and build, I have the same issue
What’s the output of whereis helix?
Mh great question, weird answer :
whereis helix
helix:
And user root doesn’t have access to helix if it’s relevant
So it’s an alias probably, what’s the output of alias helix?
Ok I missed something, I had to search for hx and not helix sry.
whereis hx
hx: /nix/store/sj7hhd4rxwc5b3m992b2cf62012wfd5q-profile/bin/hx
So, were you running helix before, or hx? If the former, I think the question about what that is still stands (maybe try type -a helix)?
I already ran hx. The program is enabled with programs.helix.enable but the executable is hx and only hx.
The command give me this :
type -a hx
hx is /home/user/.nix-profile/bin/hx
I really don’t understand, everything seems normal, it’s in my home, configured with home-manager and nothing more. I’m still making the configuration in a VM so it’s not that big, there isn’t lot of place to mess up. Helix is defined only on its dedicated home-manager module.
Other packages installed the same way, like zellij, works like charm.
Another thing, maybe unrelated, gpg hang indefinitely if I don’t use sudo, which pop a prompt for the gpg password, not the sudo on. And some software like gparted cause error if not launched with sudo, there seem to be problem with polkit I can’t resolve
1 Like
I think I found the problem. The file ~/.cache/helix/helix.log is created in read-only, but of course the user must have write access. Do you know why and how to solve this ?