madthumbs@lemmy.worldM to Linuxsucks@lemmy.worldEnglish · 17 days agoSudoeditlemmy.worldimagemessage-square41fedilinkarrow-up189arrow-down123
arrow-up166arrow-down1imageSudoeditlemmy.worldmadthumbs@lemmy.worldM to Linuxsucks@lemmy.worldEnglish · 17 days agomessage-square41fedilink
minus-squaretheunknownmuncher@lemmy.worldlinkfedilinkEnglisharrow-up3arrow-down1·edit-217 days agoSometimes 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.
minus-squaremadthumbs@lemmy.worldOPMlinkfedilinkEnglisharrow-up2arrow-down6·17 days agoWe 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?”.
minus-squaretheunknownmuncher@lemmy.worldlinkfedilinkEnglisharrow-up3arrow-down1·17 days 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?
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.
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?”.
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?