-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pikaur is ignoring $EDITOR #741
Comments
what the output of also install latest |
Well, there we have it:
(as a note: without specifying the And for the logs:
So that explains the "bug". Thanks for the help! Update: I fixed it by specifying to preserve the EDITOR in the sudoers file, but since I didn't needed that before, I'll let you choose if you want to chose the issue or not. |
weird - did you previously altered your sudoers file? i have default config file from arch linux and it being preserved, so in the first case i'm seeing output of EDITOR set in the current user, not in root |
No, I never edited it before. I use endeavour, not pure arch, but it should be globally the same file I think |
that's weird, but since i can't reproduce the problem in arch - i'm closing this one |
Same issue here, using Manjaro.
My fix is add the following to
|
For me, the culprit was |
i wonder, if it would be better then to spawn commands with some different sudo flags? |
Running the editor as user would be ideal imo. With |
no, preserving all env variables (-E) wouldn't work in this case:
because in that case all your env variables would end up in pacman, while it should be running with root's env vars |
and this is a good point - i've just realized that during build and during PKGBUILD review editor command is not changing the user properly, i'll fix this |
I see. Maybe |
please don't do any suggestions, if you don't know for sure |
I read the man page and from my experience it looks like a reasonable solution. But I haven't read the source code of pikaur from start to finish nor did I try every possible user configuration to make sure this is definitely the way to go. Maybe I will, but probably not. My first suggestion was under the assumption that pikaur is run as user and elevates privileges only for pacman, which is not unreasonable to assume. |
that's described in readme, reading is usually more effective than asuming ;) |
Description:
pikaur is ignoring my editor when I want to edit the list of packages to update (as shown above), or when I want to edit a PKGBUILD file.
nano
is opened while my editor is set tonvim
(and the root editor tovim
).I don't know why nano is picked over nvim / vim, though…
Attached log:
You'll find:
nano
is opened when editing what to upgradepikaur --version
echo $EDITOR
(I dropped a few lines, but they weren't relevant imo)
Thanks!
Update: I didn't have the problem with
pikaur 1.17-1
, which was the installed version until yesterday on my machine, according to pacman logs.The text was updated successfully, but these errors were encountered: