this post was submitted on 01 Nov 2024
65 points (77.3% liked)

Linuxsucks

209 readers
105 users here now

Rules:

  1. FOSS advocates and Linux evangelists aren't welcome. -We ask that you block us.
  2. Moderation is heavy handed. Try to stay on topic (that is LINUXSUCKS!).
  3. No Complaining Mute the sub if users, content, or rules bother you *it's ok to report rule violations

founded 2 months ago
MODERATORS
madthumbs
Uschteinheim
65
Sudoedit (lemmy.world)
submitted 1 month ago by madthumbs to c/linuxsucks
41 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] madthumbs -5 points 1 month ago (1 children)

TBH, I rarely noticed the warning from nvim. I did get in the habit of learning when to use sudoedit though.

[–] theunknownmuncher 2 points 1 month ago* (last edited 1 month ago) (1 children)

Sometimes I overlook the warning too, to be completely honest. But when that happens, I think "oh, my bad" and not "this is Linux's fault!"

I'm sure that you can restyle the warning in vim so that it is more eye catching, but I've never tried.

[–] madthumbs -4 points 1 month ago (1 children)

We can't very well honestly call Linux 'new user friendly' with issues like this that many of us are familiar with. Another legit attitude to have is: "what do you expect for free?".

[–] theunknownmuncher 2 points 1 month ago

We can't very well honestly call Linux 'new user friendly' with issues like this

I agree that editing system configuration files with a text editor is not 'new user friendly', but that is true for all operating systems, no?