-
Notifications
You must be signed in to change notification settings - Fork 6
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
Is the concept corect? #11
Comments
I can open it as user root.
So I could not understand what the problem was there. |
No problem, my English is also not very good :) I try again:
How can I edit the file then? As step 3.1 I need to disable read-only-mode. For "Auto-sudoedit", my idea was to change the algorithm:
Sorry; is it more clear now? |
I think auto-sudoedit is currently working with that algorithm, so I don't know why it doesn't reopen. |
My apologies, I may just not understand the idea behind auto-sudoedit, but I do have difficulties understanding the idea behind it:
Shouldn't auto-sudoedit instead intercept the "find-file" function and say "hey, you won't be able to edit/save this file, do you want to open it as root via tramp instead"?
The text was updated successfully, but these errors were encountered: