Linux

nano but i'm a casual. i can use vi/vim in a pinch, but i'm inefficient. ed and emacs are totally foreign

i tend to use a graphical text editor like Kate unless there is a specific reason to do it in the terminal

another vote for Neovim!

Big fan of Helix. Best part is that it dose not need any plugins to be a modern editor. Just configure any LSPs you want and it all just works including things like fuzzy finding, multiple cursors, file browsing etc.

I use nano for quick edits. I don't know more than the basics of vim, and don't do a lot of editing on the terminal so I haven't needed to.

Micro, for muscle memory for keyboard shortcuts from when I was a mostly GUI user.

Just echo text to create a new file or use sed and awk to edit an existing file.

In reality, I use nano for edits and vimdiff for comparing files (usually a .pacnew after an update on a headless device)

Neovim, configured entirely through nixvim. I always liked neovim, but it's never been as incredibly stable as now with nixvim.

Main/only IDE both in private and at work. Can't ever go back, muscle memory has ensured that.

Nano 4 life

What to do other than installing nano and changing visudo?

suffer.

isnt the whole point we get to use the tools we want?

My first experience with *nix was a professor leading me into a server room though two biometric locks and setting up the config files for a compute cluster faster than I would have been able to open the files.

He was using Vim, and though it took me a while to learn, the sheer speed with which he was able to get us out of that unbelievably noisy server room sold me for life.

Well, I use vim for text edits and nvim+extensions for an IDE. As close to a vim purist as is reasonable. But frankly, it's the first one you learn to use well.

Been using linux full time for 10 years. I do almost all of my system admin stuff in the terminal (my desktop, laptop, home server with a few containers). But i cant for the life of me figure out vim (like i know how, but it just doesnt click for me or feel natural)... i tried a bunch of times and will keep trying... but until then, its (shamefully) nano for me

My first computer was an Amstrad 664, with a green screen. I’m old. And I’ve been around Vim and EMacs from time to time and I love the console but for the love of god, since GUIs became the normal way to interact with computers, I just install micro now and have the same hotkeys across all the modes of interaction.

Speed of typing really isn’t the defining productivity measure for code.

Now I use VS Code in a GUI and micro on the console and that provides a reasonably consistent way of interacting with text.

I have been learning vim specifically because of VimWiki. It’s always fun getting a few words into writing a document before realizing I wasn’t in Insert mode, then I have to figure out what I messed up.

Nano. It's the easiest to use

When I first started using Linux I used Kate, I know, I know, not command line, but I didn't needed a command line editor for my own computer. Eventually I started using nano for quick edits and that became my default CLI editor for a while. I don't remember what I used as an IDE back then, but maybe it was Eclipse, although I think it was mostly just Kate.

Eventually I decided to learn either VI or Emacs, and a friend who used Emacs pushed me to that side. I ended up switching everything to emacs, CLI, IDE, I even learnt org-mode and had tables and presentations in it.

Eventually my pinky started to hurt too much, so I switched to Pycharm for python, and kept emacs for C++, text edits and org-mode. I ended up slowly switching emacs everywhere and reverted to nano.

Some years back I decided to properly learn vim. I have been using nvim for a few years, and while it's not the everything tool that emacs was for me, it's still pretty darn useful. I also haven't become a movement ninja and oftentimes I go wwwwww to get where I want to be. But still, there are some very nice shortcuts that I use a lot like Change Inside/Around or Delete X lines. Macros are cool, and sometimes feel magical, but other times they don't work like I expected and I can't figure out why. I don't see myself changing to something else, the ubiquity of vim shortcuts in other programs makes it very convenient when I have to use something else.

vi, since it's ubiquitous.

nano, vi, geany, kate...

I prefer nano - simple to use & always available. I manage remote systems often from my mobile using termius: config file editing, writing simple scripts for some analysis/automation tasks and recording task notes and status. Using a tablet I might use vi but generally prefer nano.

Micro is pretty nice, has limited mouse support in the TUI line numbers highlighting. That or Neovim customized

Helix: Barely needs a config. But they are also pretty close to done with a plug-in system for the stuff that isn't implemented by default :D

I use the vi family of text editors in a CLI environment because it is part of the POSIX standard.

Even if nano is the default, vi will be there too, and I can just use that. Plus, if you know some basic vi commands, then you can get by without nano, and you don't need to know nano to use it for basic stuff as it shows you the key combos.

Used to be vim back in the day, neovim with a few lsp plugins — hated the convoluted collection of config scripts — then into vis (modernized vim/sam hybrid) but now settled on helix. After a small adjust for some finger memory, I wouldn’t go back. A lot of quality of life features out of the box.

I just a modal editor that just works with some quality of life features as codebases I worked on grew in complexity.

I typically use nano for the quicker edits but enjoy using vim otherwise.

sed forever

For novelty I do install msedit, because nostalgia is rose tinted. But for realsies it's vim, not because I'm good at using it, but I'm familiar enough.

If we're talking purely something basic to be able to edit some shit on the system i think i would choose nano, purely because i've used it for years to edit everything (yes, even config files in full programming languages lol) and thus i'm very familiar with it. If we're talking anything terminal-based in general, i like helix as a modal editor. I chose it over neovim at the time because i didn't feel like configuring the whole thing, and helix is pretty much ready to go with lsp and everything ootb. A few weeks ago though i decided to make the switch to emacs, since i use guix now, so it felt like a natural fit. I might check out emacs in the terminal at some point, but i'm sticking with the gui for now.

I use vim. I learned it because I started on a bunch of hosts where I couldn't install what I wanted. But unless you have a similar restriction, go ahead and install what you like.

It's a good idea to play around with others to see what they have to offer, but at the end of the day, you do you

Mostly Neovim and Nano. Tried out ed in the UNIX4 tape that got recovered, was strange but fun to see where sed, grep and other commands got their name from.

GUI is still good old Sublime Text, but I almost completely switched to terminal based editors, I guess because of the nice work flow.

Nano because like why would I bother with anything else? It's just a quick and dirty text editor.

kate textfile &

Team vim, but I've been using Helix instead for a year or two -- it's like if Neovim and Kakoune had a baby.