Which text editor do you use?
The reasons us elders use VI is because on a new installation, it was the only thing available until:
-
You are lucky enough to find a compiled version of PINE/PICO, or
-
You have the compiler installed, and can get the source code and build it yourself.
For some reason, some elitists decided that if you don’t know that, then you are a failure. But honestly, when modern distros started coming out with WYSIWYG-type editors, it was a relief, even though I reverted to VI/VIM because of muscle-memory, I do not push it on new users. It’s the same argument people make for driving manual vs automatic, sure it’s useful, but when was the last time you even saw a manual car? (At least in North America).
You want to live dangerously, go ahead and put NetBSD with just the basics and leave the rest of us who want to do something useful alone.
-
Nano because I’m too lazy to learn vim or emacs. I want something that works and not something that operates like cheat codes in old video games.
I use
- sublime-text when not confined to a terminal
- nano for example with git’s CLI
- vi/vim when the others are not available.
dd or GTFO.
head n-1 > tmp && echo “line replacement” >> tmp && tail -n+1 >> tml && mv tmp orig
It’s worse than the picture depicts. It’s not just the lovers, the elitists and the evangelists, it’s the sheer range of choice too, beyond the loudest.
My distro came with Nano, so here I am
I’m using vscode.
Only Fresh
kate when I am using GUI and vim when I am using CLI.
i miss notepad plus plus, that’s pretty much the only thing i wish i still had from before linux though.
@cyclonedusk@lemmy.blahaj.zone Notepad Next is an alternative to Notepad++ in Linux. Here a (german) article from @gnulinux@social.anoxinon.de :
Gedit
I just found that notepadqq is no longer maintained. :(
You and I both. I have nostalgia from years of using it in grad school for R. I found Kate is pretty close, but NPP runs fine in Bottles.
Gedit, mousepad, geany or kate may help you forget Notepad++, which is truly great software.
First choice: use a normal damn GUI text editor
Second choice: Nano. It’s simple and comprehensible, and a best CLI choice for newbies. You can then turn to vim, emacs, or whatever, but don’t make your life harder from the get-go
People suggesting to start with Vim are probably the same ones pushing for Arch as a first distro. C’mon.
That’s how you breed scrubs who can’t M-x-butterfly. I say give them a distro that boots into vi and starts a background process that block internet access around them. If they manage to quit vi and kill the daemon, they’re ready for Linux.
Lol
use a normal damn GUI text editor
The right choice as long as you don’t want to edit code/config files. Trust me, writing code inside libre office is not fun.
Libre office isn’t a text editor it’s a document processor; more like a gui for something like TeX, or realisticially html, than a program for reading/editing plain text.
Kate is a basic GUI text editor that can highlight syntax, suggest options and do other things useful for code and configs. Comes with KDE (which is a common newbie recommendation) and is available as Flatpak everywhere else.
But sure, there are instances where you should use CLI text editors. If you need to edit text files as root, this is generally the best option. Also, it’s the only option for headless setups and SSH. For that, nano will do.
Was gonna write that only one true text editor exists. But okay, you are right, of course
I feel called out but the only time I’m editing a file is tweaking a config or .env file and its just so simple for me
signature look of superiority
I think it comes with a text editor already built in. I don’t need a text editor though.
All I’m gonna say is than nano is installed on almost every Linux os and has the keyboard shortcuts written on the UI.
Who doesn’t have vi/m?
Fwiw, helix also gives visual feedback on bindings if a key is a table for mutiple bindings.
I’m sorry I don’t see how that’s relevant to my point.
I’m saying that of all the text editors, nano is the one that usually takes the least amount of effort to learn and set up. Both of those options require either learning or set up, so why would I choose them if convinience is what I’m after?
I was just asking which distros don’t have vi/m. The helix point was an aside. It wasn’t combative, just curious.
I wouldn’t know tbh. I’ve never had any reason to use anything other than nano for a terminal text editor.
When I uninstalled Windows and switched to Linux (CachyOS (which is Arch BTW)) I also took the time to free myself from VScode to completely escape Microsoft’s fuckery.
I learned how to use Neovim. I’ve got a configuration that I really like and I took care to make it portable enough that I can just copy over the init.lua file to set everything up on a different computer.
However this is only earned through weeks of Lua hell. You are effectively building your own editor from almost the ground up. I only recommend Neovim if you want the first medium scale project you work on to be Neovim itself.
