I use to use vim but I discovered org mode so I use emacs.

Recently I been doing programming on plan 9 so I been using acme.

Yes! Neovim for coding, Vim for non-code editing

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"  

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

Yes I do and to my delight I' ve yet to encounter a situation where I can't use the editor I prefer anyway. Joy.

Yes. But mostly IdeaVim in JetBrains IDEs though.

For those that haven't yet learned vim: the real power is that the commands can be combined to form a mini-language. Commands can also be recorded in macros and replayed. This is what makes it so awesome. But to really make use of this you have to properly learn it, only knowing i and x isn't enough.

Neovim for any text editing including code, but this thread tempted me to try helix.

Yes, started using vi when I started using a Unix login at university. That was in about 1994 or so. When I started using Linux it was definitely vim.

I've tried using evil-mode and vim keybindings in other editors. I somehow keep coming back to vim, though.

Started on vi, stayed in whatever has vi/vim bindings available.

The more I can stay on home row keys the better editing text is.

Nah, I'm another nano guy. You can set up syntax highlighting for it you know?

It's not that any one is better than the other, it's up to your use cases. I've learned vim a few times in my life already (and mostly just know the hjkl bindings from playing tons of terminal roguelikes) but it always decays because I don't put the knowledge to use. Because it just doesn't fit my use case.

I write small scripts, some Python and stuff and I'll usually use PyCharm to debug that these days. So nano is relegated to the small tasks like config editing or quick, in place fixes to scripts.

You almost always have nano or pico available, so it's really unlikely that you'd get stuck with nothing but vim, unless you just didn't know that nano existed.

Yes in SSH terminal,

Yes in vscode,

Yes because I use TUIs that use all the same bindings and they're great one you get the vocab.

Yes as Hyprland bindings, k9s, etc etc etc etc

nano for most editing

vimdiff for comparing files (Ie .pacnew files)

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.

I'm at the point where I'm considering moving to vim because I'm sick of the lack of good defaults on Nano and Micro for quick edits, and I'm also tired of IDEs breaking my flow with poor defaults that pop open UI components which must be navigated differently depending on what it is, or just switching back to the mouse every couple seconds.

Just haven't made the jump yet because I want to sit down and go through all the hot keys in one go, including for global stuff like tmux, the DE, etc.

I have never been on a machine where I can't install and use nano. I can use vi / vim / nvim, but I don't have muscle memory. I have tried to convert away from nano, but it's just too easy and what I have been used to over nearly 2 decades on Linux. I have nvim installed with a few plugins and a bit of a custom config, but anytime I need to do something important or complex I jump into nano. If I remember and am not in a rush I'll jump into nvim to try and practice.

I prefer NeoVim, but now I'm trying out Guile Scheme, and the best Lisp support is in Emacs from what I understand, so I'm currently attempting to stop using Vim commands in Emacs.

Nano for low-level system crap (config, scripting, etc) and Obsidian/Typora/Insert WYSIWYG editor here for major writing. I'll utilize LibreOffice if I need something done in a Windows-compliant way.

neovim at home, Zed with vim bindings at work because I'm stuck with a locked-down Windows machine.

I can still speak vim, but I drive helix daily.

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.

No, but I'm interested in using something more advanced than nano but I have no real need to.

I only use vim when it’s the only option… so like 99.9% of the time 😞

full vim. It always messes with my muscle memory when vim-tiny is installed as a replacement.

I do not use it as my default text editor but I use it practically every working day. Plenty of times it's the only thing I have available to me. Pretty often vi is all I have to work with

Been using micro.

No. But only because I switched to helix. I have used vim for a lone time before that. Only having vim on a system is fine. Far worse is only having vi. Which is almost like vim but missing a lot of useful things.

Yes, yes, and have been in a situation where the only editor available was nvi (not vim). ed(1) rocks when on slow connections to low-specced boxen, btw.