I’ve been using Vim for 20 years.

I only opened it once and I haven’t been able to close it yet

nano

I keep it holy with Emacs

For much, not for all.

System and user files are pretty close to one another in NixOS, so I use it for both. Sudoedit is set to vim, but I have a kitty and neovim (technically it’s nnot nvim, it’s nvf so I can config it in Nix instead of Lua) environment that tiles quite nicely and uses nonconflicting keymaps.

I use mod+hjkl for navigating my window manager, too, which has led to an interesting situation. Hyprland just migrated to Lua from Hyprscript, and Neovim uses a lot of Lua for inbuilt commands and stuff, so you’d think I’d be thrilled to write them both in the same language. Instead I just sigh at the greener grass because I already configured them both in Nix.

I do use Obsidian (with Vim binds, and monospace source mode as default for everything except tables) for my markdown viewer / primary notekeeping cloud sync, and Kate for previewing media that needs to be formatted right as a .doc or .pdf.

Some Obsidian notes are handled with Vim, actually. I have a script that sets up a new Zettelkasten note with automatic tags and opens it in Neovim, because I find it faster than Obsidian when I have a single thought and need to write it before it’s forgotten. Thanks ADHD. I write Zettelkasten like little scripts of code - unique, atomic, referencing and importing each other, with a unique version history, and Vim’s great at that.

i mean vim is fine and all and i can get around it fine but nano superiority

# ── behaviour ────────────────────────────────────────────────  
set autoindent  
set atblanks  
set casesensitive  
set constantshow  
set cutfromcursor  
set historylog  
set indicator  
set linenumbers  
set minibar  
set mouse  
set nohelp  
set positionlog  
set smarthome  
set softwrap  
set speller "aspell -x -c"  
# set suspend  
# NOTE: Removed in nano 7.x; CTRL+Z suspend is now always enabled by default.  
# Kept here for reference in case of older nano versions.  
set tabsize 2  
set tabstospaces  
set zap  

# ── backups ────────────────────────────────────────────────  
set backup  
set backupdir "~/.cache/nano/backups/"  

# ── syntax highlighting ───────────────────────────────────────  
include "/usr/share/nano/*.nanorc"  

No, I use Neovim. But this I use 100% of the time.

Yes I love using neovim it feels better having an editor, agent, and cli in separate terminal tabs instead of having one program for all three

Yes. I also use vim here (in this Web textarea where I’m typing this answer) thanks to Tridactyl.

Sorry my hands are busy

`C - x 2’

C -x C-f ~/.emacs.d/init.el

C-x C-s

I’m a freelance linux it nerd. I figured I better get used to vim/nvim because every company I visited had different tooling available but their servers ALWAYS had vim.

Now I have a nice .vim setup I can easily copy/paste and work easily and fast. I’ve become quite adept in the years following that decision.

Plus, as a freelance dude using vim quickly and flying through code bases makes it really seem like I know what I’m doing / hacker type … I don’t. And I’m no hacker… But the customer is happy soooo :-)

P.s. I’m currently trying out the Zed editor with vim bindings. They are emaculate!

I used to use vim pretty exclusively, I’ve since switched to neovim. There have been a few cases where vim/nvim weren’t available but regular vi was and I’ve used it to edit text files. I imagine there were other editors but I’m so accustom to how vi/vim/neovim does things that I can’t imagine using anything else. Sometimes someone will try and convince me to use a new editor and I’ll try it but generally end up switching back to nvim. Even vi compatibility mode doesn’t really help because I use a bunch of plugins.

VSCode/Codium with vim mode. Regular vim if I’m stuck in text land.

I haven’t tried neovim. Supposedly that could handle everything I need out of vscode, but it’s easier to not be an odd one out at work.

nano for most editing

vimdiff for comparing files (Ie .pacnew files)

I switch between Nano and Vi depending on what machine I am on and if I remember if Nano is installed.

In college, my advisor/boss was basically the emacs guy, so I picked up enough to do some basic text editing but didn’t go further because I didn’t feel like spending hours reading man pages.

Later I worked at a place where a shared computer only had vi, so same story. I learned about a half dozen commands and left it with that.

Then I went though a series of other editors and IDEs at different jobs, Notepad++, StyledEdit, CodeWarrior, CodeComposer, some weird proprietary Netbeans based thing, VS Code, etc. I still used vi for minor config editing on the occasional remote machine.

Then I got a job where I would be doing a ton of work on headless remotes, so I decided to get serious about learning something purely terminal based. I tried a couple of things, but ended up with Helix because:

1. it runs pretty great on my 15 year old laptop
2. the vi commands I remembered worked
3. it has actual command discoverability out of the box
4. I didn’t have to install 153 plugins and write a 2834 line config file to make it useful

Now I’m all helix all the time and really enjoying it.