this post was submitted on 25 Apr 2025
621 points (98.0% liked)

linuxmemes

25797 readers
166 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Albbi@lemmy.ca 11 points 2 months ago (5 children)

    Why memorize a different command? I assume sudoedit just looks up the system's EDITOR environment variable and uses that. Is there any other benefit?

    [–] moonlight@fedia.io 12 points 2 months ago (1 children)

    It doesn't edit the file directly, it creates a temp file that replaces the file when saving. It means that the editor is run as the user, not as root.

    [–] Albbi@lemmy.ca 3 points 2 months ago (2 children)

    So it opens the file in your editor, since you have read access to it. Then saves your changes to a temp file. Then when you close the editor it does a sudo mv tmpfile readfile?

    I checked this by checking the file ownership when running touch myself. The file is owned by root. sudo nano myself also creates a file owned by root. sudoedit myself bitches at me not to run it in a writable directory.

    sudoedit: myself: editing files in a writable directory is not permitted

    So I ran it in a non-writable directory and the resulting file is still owned by root.

    So is the advantage of sudoedit preventing a possible escalation of privileges situation?

    [–] russjr08@bitforged.space 6 points 2 months ago (2 children)

    For me personally the advantage is that since the editor is opened by your user, it has all of the same config that I'm used to (such as my souped up Neovim config).

    Whereas if you sudo nvim /path/to/file then the editor is opened as root and you don't have the same configuration.

    [–] Albbi@lemmy.ca 4 points 2 months ago

    That's a pretty big advantage actually. Thanks!

    [–] gi1242@lemmy.world 3 points 2 months ago

    I just make /root/.config/nvim a symlink to ~/.config/nvim and running nvim as root gives me all the same settings I'm used to. (I'd rather not run nvim-qt as root though, so in that case sudoedit is useful.)

    [–] moonlight@fedia.io 2 points 2 months ago

    Yes, and it also lets me use my neovim config.

    [–] korthrun@lemmy.sdf.org 7 points 2 months ago* (last edited 2 months ago) (1 children)

    I know this is a meme community, but a modicum of effort IS warranted IMO. https://superuser.com/questions/785187/sudoedit-why-use-it-over-sudo-vi is the top result of a search for "why use sudoedit" and a pretty good answer. "man sudoedit" also explains it pretty well, as shown by another commenter.

    [–] Albbi@lemmy.ca 4 points 2 months ago

    Hey, even memes can lead to learning opportunities!

    [–] morbidcactus@lemmy.ca 6 points 2 months ago

    From the arch wiki

    sudo -e {file}
    

    Set SUDO_EDITOR in your profile to the editor of your choice, benefit is it retains your user profile for that editor, it's also less to type. For stuff like editing sudoers you're supposed to use visudo to edit that. Others can probably give better/more thorough reasons to consider it.

    [–] sanderium@lemmy.zip 3 points 2 months ago

    Correct but it uses the SUDO_EDITOR environment variable. The benefit is more security while editing system files, it creates a temporary file and when you finish it writes changes to the original. There is more to it but that is all I know, it prevents some exploits.

    [–] bitchkat@lemmy.world 1 points 1 month ago

    I believe sudoedit disables being able to spawn commands from the editor. In vi, I think it was :!