You're viewing a single thread.
nano is better than vi, change my mind.
Vi yes, vim no
sam > vi > nano > vim > emacs ed is the standard editor
helix!
There's nothing to change. Nano is better designed, but vi is a more powerful tool.
Nah, micro is the superior option! 😜
Jawohl, Jawohl ...
Micro gang rise up!
Micro or bust!
Why we have to care much about software usage. This is the current issue of linux communities, which decrease user qualities.
Our enemy Microsoft and other "big tech" laugh people like these. They are using linux just like they use windows, even bring the bad, flawed windows culture to linux.
Don't let the enemy to laugh at us.
even bring the bad, flawed windows culture to linux
Infighting is on the Unix culture since it left the Bell Labs. Or maybe even sooner.
But the only real enemy of that set is NVidia.
Linux is just a tool, like a hammer or a 3-d printer. Getting dander up over someone's choice of tool is wasted energy.
correct
It pairs with the perils of gumshoery, dear Watson. [|8>
But the only real enemy of that set is NVidia.
The only?
(Windows user that switch to linux and then say: we only need partition for / and /home are also enemies. Windows user that have switch to linux and use root for every task are enemies.)
Are those ex-Windows users slowing you down in any way?
And anyway, if you are talking about desktops, I've been using only / and /home for about 20 years since I noticed that /boot and /var didn't bring me any value for a really long time. I'm currently wondering if I shouldn't ditch /home.
Wow, I can't believe I'm reading that first point from a 2018 comment. I'd mock it if it was in 2006.
You should have backups. Not hedge against 1 in 10 million error conditions.
The second one is a huge bother in desktops. I never not regretted trying it.
The third one is a complete non-problem.
You should have backups. Not hedge against 1 in 10 million error conditions.
if a partition isn't actively written to, it's less likely to suffer damage
The second one is a huge bother in desktops. I never not regretted trying it.
ok
The third one is a complete non-problem.
This is only a problem with OpenBSD. They never encourage using a huge single root partition, and never test it.
It have an asterisk, not a -
Nano!!!
I've known some fantastic developers that used Nano as their primary editor. It supports syntax highlighting, linting, and bracket matching (jumping to the matching opening bracket when a closing one is selected, and vice versa), which is enough for some people.
Sure, it's no micro, but it's already installed practically everywhere.
I have an alias to run nano with command-line flags to customize it for plain text note taking. I remove all the fluff and the status and shortcut lines from the editor so it's just a text field. Micro is my choice for editing remote code over SSH when I don't want to push a local file.
What options are you using?