-
Notifications
You must be signed in to change notification settings - Fork 15
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
Being spammed with errors when opening a file as sudo #44
Comments
You might need to tell me more info about your setup, how is your config being loaded when you're using sudo? Normally you have to supply |
I'm also using I'll try to see if I can find the steps to reproduce, but don't you think it's better to handle the errors more gracefully so that, in case they happen, they don't interfere with usage like this? (or maybe I'm stupid and that's what is already happening, and this is coming from something else) |
Sure, I've added a catch for all errors, please try with the latest commit |
Part of the spam was two subsequent endtry in handler.vim:
Still not working, and I'm not involving sudo/su
|
I have the same issue. An example of when the problem happens is if I open a buffer inside the |
Yep totally fat fingered that one 😅 Please try the latest commit |
It fixes the worst part, but it's still echoing a message |
@farzadmf I managed to reproduce and find the issue. The problem was a file permissions error with the default log file when switching between root and your user. @seblj That seems to be a different issue because it's triggering the old catch, can you check with the latest commit and if it's not fixed open a separate issue with more details? |
I thought it fixed that issue at first since I got a new message saying: |
Thank you @rcarriga for the super fast updates I updated the plugins, and I'll be testing, I hope I don't get the error 🤞 , but if I do, I'll update you for sure |
Hey @rcarriga Now I'm facing the same issue as @frbaroni mentioned: I've installed the vim-dirdiff plugin, and I'm opening two directories using
Didn't include the logs because I thought the error itself might include a clue to a missing |
Describe the bug
I'm on Archlinux and opening
sudo nvim /etc/pacman.conf
(which is owned byroot
), andultest
is spamming me with errors. For every motion that I do, I'm getting an error:I didn't create a log, but let me know if that would help and I can try to create one.
To Reproduce
Open a file with
sudo
and see the errorsExpected behavior
Errors should be handled gracefully and not interfere with file navigation
The text was updated successfully, but these errors were encountered: