Which text editor do you use?
The first step of any linux install is installing vim/neovim. Anything else is sheer apostasy
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 in the CLI, kate in the GUI
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.
Noobs get hit with friendly fire.
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.
My distro came with Nano, so here I am
@calango@programming.dev ed(1).
I’m using vscode.
Only Fresh
Micro.
I hate modal keybindings (Vim, Nano and Emacs, all alike; though the Object-Verb paradigm looks promising for me, but until now, nothing’s better than quasimodal CUA/spring-loaded CUA).
Also Kate and KWrite.
Kate
Kwrite
when I use kde I prefer to use this edit too
Came here to say kate! I tried a bunch of them before but kate is nice :3. And then I have nano for the terminal
Kate is by far the best GUI text editor I ever used. And unless it’s a short config file and I use nano, I want GUI. It’s not the 80s anymore!
It’s not the 80s anymore, thus I want a good TUI over GUI any day
The only sad thing about Kate? No terminal version of this beauty.
It has a few quirks I utterly despise :(
Like it cannot print invisible characters. Had a script create some broken folders with a BOM character at the beginning. I couldn’t access the files in any way except that they appeared in dolphin and ls. Had to delete them via the fucking inode.
I was forced to use VSCode (an open source fork at least) to find out what the fuck was wrong with the input file the script used to generate the folder name.
Like it cannot print invisible characters.
I was looking at an option to display invisible characters in Kate like last week. So it got better, I guess.
Only non-printable spaces from what I can tell.
The BOM character does not fall into this category and is still invisible. Try pasting it into Kate. It’s between those arrows:
---><---
Me no love nano, me brain only can use nano.
E macs scary. vim no let me leave :(
You might like micro :) its like nano but with more user friendly features like Ctrl+s for save, and clicking places to change cursor location. I think you have to enable the “cheat sheet” of keyboard commands being visible all the time if you want it to always be showing like I do
It also supports extensions but I don’t really care about that lol. I just want something simple with nice ux :)
less is more,
micro does more than nano,
many names, much confuse.
p sure latest nano can do all that, you can atleast change the default save bindings to ctrl s in the .nanorc file and im p sure most distros include a build of nano that has mouse support. If its supported by the build, its just a settings toggle in the rc file likr the bindings :)
Micro also has syntax highlighting, multiple buffers with split editors, and theming, among other things. It’s pretty dang neat
vim, because that’s how my father taught me, and how his father’s father taught him.
Choose vim! The generational trauma of file editors!
haha!
Sometimes I feel like my side of the holy war isn’t engaging in completely good faith.
I might switch sides to emacs if my fingers were long enough to reach the key combinations.
Maybe I’ll go try it, anyway!
…
What was the command to exit
vi, again…?The same as for man pages and less and a bunch of other cli tools.
Q. For Quit.
Ah, I see that your : is silent.
As a new Linux user who spends as little time editing config files as I can manage, I’m fine with nano.
I was too untilI switched to opensuse aeon and default is vim instead of nano. I just switched. I don’t care. Both are not perfect - i won’ create yet another fork just because i want to do it differently. I don’t get why vim has so few shortcuts.
I don’t get why vim has so few shortcuts.
Someone’s gotta do it. I’m leaving this comment so it’s not me.
I was playing around with Free BSD I think and the default was Vi. I was just like “yeah, no” and gave up. I didn’t have wi-fi working so I couldn’t install anything else.
I think Micro is even easier. Nano is good too though.
