Neovim + LazyVim
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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.
Micro is pretty nice, has limited mouse support in the TUI line numbers highlighting. That or Neovim customized
Kate 👀
Neovim for terminal but often I use kate for gui because I still don't find vim commands more efficient
Vim unless I can neovim.
Being able to change configs on headless systems was my gateway, now I just prefer it
Used to use micro but just switched to neovim, I'm finding it great, esp with the file manager built in
do you use neovim over vim for any particular reason?
i ask because i'm a vim user and wondering if should update but wondering if the x windows overhead is worth it.
vim forever (i think)
Was staunchly team vim for 15 years, but now I'm on helix. As another user stated below, its like if vim were re-designed today, and without needing any addons to be a code-aware editor.
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
Nano. It's the easiest to use
When I ran a trivia bot on irc back in the day, I used to use sed to edit question files. But mostly use nano now. I don’t do anything all day and COULD learn vim/emacs/something else. But I cbf
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.
NANO I just need simple, and tell an me how to save and exit without abstract key codes.
Emacs → Vim → Neovim → Helix
vi, since it's ubiquitous.
Team Vim. Because I learned the vim basics once 20 years ago and never bothered to learn after that. :D
Nano, because it's the only one I can remember how to quit from without power cycling the computer.
Top Tip: open another terminal and kill the task from there
( /s )
At the risk of restarting the Editor wars (https://en.wikipedia.org/wiki/Editor_war) from days of yore, I find it interesting that emacs wasn't even in your list of contenders. I hear it mentioned less frequently these days, so perhaps it's going by the wayside?
For the record, I'm a vi/vim user! I had the privilege of being taught to use it by an RFC-writing greybeard decades ago, and have used it without thinking ever since.
For those who find themselves on a machine with only vi/vim, or want to learn, here's a quick primer when editing a file (usually done by typing "vi foo.txt" in a shell) --
:q! ...Force quit vi (:q also works -- gentler!)
:wq! ...Save file and quit vi
i (then type characters) ...insert text at current position
A (then type characters) ...Insert at end of current line
G ...go to first character of last line in the file
/foo ...search for first occurrence of "foo" in the file (hit / again to find additional instances)
x ...Delete character under cursor
:56 ...Go to line 56
yy ...Copy the line the cursor is currently on into the buffer
p ... Paste the buffer
r (then type character) ...Replace character under cursor
u ...undo (hit multiple times to undo prior actions)
When done with a command like this, hit Esc to go back into normal mode.
Second nature after a bit of practice! I used to work with a guy who insisted on using ed. That was... odd.
Micro, for muscle memory for keyboard shortcuts from when I was a mostly GUI user.
I am a noob. My server is a MacMini running Ubuntu server because it was easy to install. I have a website, Jellyfin and nexcloud.
I don’t have the brain cells to understand VIM.
In the CLI, I use nano, always. In the GUI, I use Sublime text because the colors are very pretty.
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.
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.
kate textfile &
and what ?? don't leave me hanging
Profit
(A single & is used to detach the process. Though Qt apps keep logging)
Emacs.
With all the vimmery going around nowadays though, I feel like I'm on the losing team. ;_;

Surprise unix_surrealism
I used Neovim for a couple of years and then switched to Emacs. I love it.
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.
micro for sensible defaults out of the box, and because I don't like modal editors.