How dare you use a text editor because it's easy to use

Nah... vim users fight emacs users, but not nano users. Wrong league. We do not beat little children ;)

Nano is more like fast food. It’s easy and convenient, but it makes you feel a little guilty and dirty afterwards.
- Nano is the tool that people use when they don't have a need for TUI editors in general and therefore don't want to have to memorize how people with teletypes decided things should have been done 75 years ago and who also don't want to get dragged into endless pointless bickering arguments about which set of greybeards was objectively right about their sets of preferences.
  
  I'm glad people enjoy the editors they use and also I just wanna change a single fuckin line in a config file every once in a while without needing to consult a reference guide.
- How about micro
And yet Emacs users don't fight vim users. Emacs users decided vim's interface was pretty cool and added it to Emacs. Somehow people still call it a war though.
- Bruh 😂 the Emacs user community absolutely constantly shit on Vim users. When they added Vi(m) bindings they literally named it 'evil mode', and they constantly make fun of people who use it, and spacemacs, and the latest flavor of (neo)vi(m), and all the extensions necessary to make vim halfway useful as an ide, etc etc etc.

I once fixed my bashrc file with libreoffice

calm down satan
- I regularly fix my bashrc file with Notepad. I run it in Wine because I cbf to RealVNC from my Windows CE media server.
  
  (n.b: None of this is real, I wrote it to upset people, I'm sorry)
I prefer Office 365 online.
Come back after your uploaded it to the cloud and edited it using Google docs.

IME?
- Integrated Mevelopment Environment. You should have known this
- That acronym usually stands for "Input Method Editor" and describes the program that makes people able to type east Asian characters with a usual keyboard.
  
  日本語は楽しいです。
- The M stands for beefcake
- Integrated Memeing Environment
Vscode is malware
- VScodium is FOSS though
- ?

nano friends rise up!

I too use nano.

alias nano="vi -y"
- Just tried it in my terminal and I couldn’t exit, lol
- ln -sf /bin/nano /bin/vi
I like Nano. I think it is quite good. There, I said it.
- Edit a file, writing a quick shell script or whatever in the terminal. Nano is great. I don't see any use in learning vim or emacs. If I need something more I'm going use a gui editor anyway.
  
  Don't get triggered anyone it's just my preference
Well hello there!
Looks like you only got one so far.
- There are dozens of us!
- nah you're wrong

Micro, hell yea!
Made the switch as well thanks to the modern key bindings

nano gang

Gross
- They hate'us cause they anus.

Vim is pretty easy for me because I'm used to it. Nano is very difficult to use for me because I've rarely used it.

Same here, nano is the bane of my existence.
I was Nano user and I liked it. After I learned to use Vim, I liked it more. Now when I use nano it's frustrating to use and I can do things much faster and easier in vim 😅
Opposite here. I got started with Gentoo back in the day of building things from the ground up. Their tutorials all used nano and I just got used to using that. I think when I had casually tried to mess with linux previously, old Mandrake and Redhat in the '90s, I always used the GUI editors, but I also didn't have a ton of time to mess with it and my hardware wasn't well-supported.
- Same. Stage 1 install will forever be a core memory for me.

Sometimes you don't even have the luxury of nano. Any moderately advanced Linux user should probably learn the basics of vi. Just knowing how to insert text and save it can fix a system that's stuck in recovery. Even if it's just to add a comment in front of a line in a config file.

I do like that some distros make visudo use Nano instead.
- you can change that really easily
Sometimes you don't even have the luxury of vi. Any moderately advanced Linux user should probably learn the basics of sed. Just knowing how to insert text and save it can fix a system that's stuck in recovery. Even if it's just to add a comment in front of a line in a config file.
When does that even happen? If you have nano installed, wouldn't it work too?
- Not in rescue mode. If you can't mount your root partition because something was fudged in /etc/fstab, for example, you may be stuck in recovery and depending on your distribution, it may not have nano in that minimalist mode.
  
  For me it also happens when I install a VM of Debian using the small image, on my dedicated server in a data center. The company hosting the server requires a special network configuration and AFAIK, there's only vi. So i need to use the console to access the VM and from there, edit /etc/network/something with vi to setup the network. Once done I can reboot and install the rest of the software over the network, including nano.
  
  I've been using Linux for more than two decades. Before nano I was using pico, but it also required to have pine/alpine installed. So knowing the basics of vi has often been helpful over the years for me.
  
  Maybe it's because I like tinkering with VMs and SBCs, and most people will not encounter situations where they don't have nano, but it can happen. And you'll be glad to know at least "i" and ":wq!".
- In a professional context, you might end up on servers that don't have nano installed, but do have vi. Or if you're helping out a friend on their laptop, they might not have the same software as you. Or if you often end up tinkering with random devices and/or setting up new systems it might be tedious to install the same applications every time.
  
  It's basically an argument for learning the very basics of the most common editors so you have flexibility no matter where you end up. Even when you have the ability to download and install your preferred software, it's still an extra step that might not be desirable for a variety of reasons. But if it's just your own personal device, I see no problem with just installing whatever you prefer and running with it.
  
  EDIT: Personally, I find that I don't end up using those other editors often enough to remember the abstruse commands of tools like vim, so I'm not worried about it. When it does happen, 99% of the time I can just whip out a smartphone and look up the directions for the n-dozenth time.

I’ve come to the conclusion, people who use vim just continue to do so out of a stubborn sense of pride for finally learning the key combinations.

In my case it's not a sense of pride. I can't use anything other than Vim because I keep accidentally putting random incantations into my word documents.

"There once was a dduuuZQ:q!"
- haha, same. do you use vimium as well?
I mean, yeah, kind of. In the same way pilots fly planes out of a stubborn sense of pride for knowing what all the flight deck controls do.
I honestly learned it just because I hated having to change hand position to use a mouse.
- Can you use a mouse in nano? I always just use the arrow keys, or page up/down and home/end
  
  I mostly use vim but I barely use the jkl; to navigate the document.
I am faster, more comfortable, and more productive in Vim. I use the same keybindings in all my editors and IDEs. It's okay for people to have different preferences.
It's just convenient that it's pre-installed on many servers.
So I can use it now everywhere with my stubborn sense of pride for finally learning the key combinations.
What do you mean? The vim users know their key combinations pretty well, that's kind of the point of vim.
That's funny, I feel the same way about Excel users.
Somehow it seems this would apply to any linux user
It's not pride, it's just that I know how to use it really well and that makes it easy for me to use.

But it's really only for viewing files on another system over SSH. For local work I use Sublime Text
I just use vi

Is that stupid? It's all I ever bothered to learn, hasn't failed me yet. Now I'm not some big time linux guru but I'm a sysadmin and regularly find myself elbow deep in a CLI for stuff.
When you only need to hammer a nail every once in a while, any hammer will do. When you're a roofer, you better have a roofing hammer.

If you don't spend your life in a terminal and just need to edit a file, vim isn't for you. If you want to learn complex strings of arcane wizardry to not only make your life easier but amaze your underlings, use vim.
no, modal text editors are just nicer to use
There is no sense of pride. Every text/code editor has key combinations that many users will learn eventually. Vim has easier key bindings.

Vim (or emacs, or any other advanced text editor) is much easier to use than nano when you need to do something more complex than type couple of lines.

Better? Maybe!

More efficient? Surley!

But easier?! Hell no! Easy means you can use it without a lot of training or studying. It is self explanatory. And there is no way on earth that vim is easier than nano. I don't need to know anything to use nano I need to check docs for hours before I can even start using vim
- This makes it seem like jerking off to MILF porn is hard because there is a learning curve
- It is easier after you learn basics. Learning is not easy, but usage is.
(...once you learn the bindings)
And how often does that happen in the real world?

VIM may have been a very useful tool 20 or 30 years ago, but today it's nothing else but a tool for one's sense of superiority. It's the vinyl of editors.

If you have to type that much code in a terminal, your infrastructure is outdated. Simple as that.
- Every day in my case, except holidays.
- You seem to believe that people only use the terminal if they HAVE to. I doubt anybody these days HAS to type any amount of code in the terminal, but choose to anyway. Like probably anyone else I have access to modern tools and infrastructure, but I choose to do work in the terminal because I’m more productive there. I use (neo)vim because I like it more than any other text editor I’ve used, and have no problem writing code and debugging in the terminal.
- Yes it's so outdated that mostly every IDE offers usage with its keybindings.
- VIM may have been a very useful tool 20 or 30 years ago, but today it’s nothing else but a tool for one’s sense of superiority. It’s the vinyl of editors.
  
  So, because you don't understand something, it's outdated?
  
  If you have to type that much code in a terminal, your infrastructure is outdated. Simple as that.
  
  Ok, I can see you have no idea what you're talking about.
- I actually use VIM bindings in PyCharm, slightly cursed but actually works really well and meshes fairly nicely with the other IDE shortcuts. Being able to use it in any terminal is a nice bonus.

You noobs. I just use combinations of cat piped to sed to edit my files, which are mainly lisp code.

- cat pipeing is safer though.
  
  foobar > file and your file is gone.
- <file foobar
Amateur! I write my code down on a piece of paper, scan it in, send it to my computer through email, then make a custom-built AI read the paper and print it in the terminal!
- M-x M-c butterfly

Average vim user: vim is easy.

Also average vim user: literally hours of reading tutorial pages on how to use vim.

Allow me to present to you my Ultimate Guide to Emacs.
- You can learn Emacs in one day. Every day.
It is easy, though? I cannot even use it correctly. I just know some of the commands and that if you hold down shift it goes backwards.
- I'm a vim user and I would say it's not. It's very powerful, but only once you become familiar with the commands.
  
  Nano is a better default for the average user because it works in a way most users would expect for a text editor to work.
- Honestly, these days it's pretty simple. The thing you need to remember is that you do not need to know EVERYTHING all at once. Learn a little bit, use it, keep what you use, discard what you don't, get it in muscle memory, and learn a bit more. Very quickly you'll be zooming through vim.
  
  You can learn the basics, and go from there- the basics of vim (which imo everyone should know- vi is often the fallback editor), and then you can just casually learn stuff as you go.
  
  Here's the basics for modern default/standard vim: Arrow keys move you around like you expect in all 'modes' (there's some arguments about if you should be using arrow keys in the vim community- for now, consider them a crutch that lets you learn other things). There's two 'modes'- command mode, and edit mode.
  
  Edit mode acts like a standard, traditional text editor, though a lot of your keybinds (e.g. ctrl-c/ctrl-v) don't work.
  
  Press escape to go back into command mode (in command mode, esc does nothing- esc is always safe to use. If you get lost/trapped/are confused, just keep hitting escape and you'll drop into command mode). You start vim in command mode. Press i to go into edit mode at your current cursor position.
  
  To exit vim entirely, go to command mode (esc), and type :wq<enter>.
  
  ':' is 'issue command string',
  
  'w' is 'write', aka save,
  
  'q' is quit.
  
  In other words, ':wq' is 'save and quit'
  
  ':q' is quit without saving, ':w' is save and don't quit. Logical.
  
  Depending on your terminal, you can probably select text with your mouse and have it be copied and then pasted with shift-ins in edit mode, which is a terminal thing and not a vim thing, because vim ties into it natively.
  
  That gets you started with basically all the same features as nano, except they work in a minimal environment and you can build them up to start taking advantage of command mode, which is where the power and speed of vim start coming into play.
  
  For example 'i' puts you in edit mode on the spot- capital i puts you in command mode at the beginning of the line. a is edit mode after your spot- capital A is edit mode at the end of the current line.
  
  Do you need these to use vim? Nope. Once you learn them, start using them, and have them as muscle memory, is it vastly faster to use? Yes. And there's hundreds of keybinds like that, all of which are fairly logical once you know the logic behind them- 'insert' and 'after' for i/a, for example.
  
  Fair warning, vim is old enough that the logic may seem arcane sometimes- e.g. instead of 'copy and paste' vim has 'yank and put,' because copy/paste didn't exist yet, so the keybinds for copy/paste are y and p.
- Vim makes it easy to edit text in complicated ways, once you've learned it.
  
  Vim is not easy to learn nor intuitive.
  
  It is simple and compounding.
  
  You might not ever edit enough text to ever need to learn a new skillset to edit text. If that's the case, use nano.
  
  But if you do find yourself editing a lot of text, consider trying vimtutor.
  
  It takes 20 minutes and you'll be proficient enough to match nano's efficiency ceiling.
It's extremely easy to get started
- VIM is like drugs. Easy to start, hard to quit.

The Terminator is not here to kill you, its here to protect you from Emacs (which can change its form to anything).

Cmon dude, what's most likely to be Skynet?

Vim: Clearly evil, lightning fast. Relies on vimscript for any interactivity and can barely be used outside of the editor.

Emacs: the hippie brain child of some of the brightest minds at the MIT AI lab, funded by military contracts. Slow, but uses a near-universal language that can easily escape the bounds of the editor, (and often does (, and holy shit where did those parentheses come from. (Oh no, it's becoming self-aware - fly you fools....!
- Vim: Clearly evil, lightning fast. Relies on vimscript for any interactivity and can barely be used outside of the editor.
  
  I don't know why you want use Vimscript for anything outside of the editor. But if that your issue, then there is Neovim. It uses Lua instead Vimscript, but what is the benefit of using Lua outside of Vim? That changes nothing.

In every post of this kind I am amazed at so many people using nano instead of micro which is SO MUCH BETTER while being the same thing at the same time.

When you help manage thousands of servers with vim and nano already installed, it's just faster to use one of those than installing something else nearly ever single time.

I prefer nano for quick edits of small files, but vim for hunting down things in larger files.
- Or you can preinstall micro like you preinstall everything else 😅
Holy cow. You can use your mouse with micro. Amazing.
- You can have mouse support with nano. Alt-m toggles it on or off.
- And all the shortcuts are SANE, not the weird thing of nano
I’ve discovered it just a few days ago and now use it on all my machines

The best text editor is ‘$EDITOR’.

I think you mean "$EDITOR". Gotta have that variable expansion.
- Not necessarily! I always run ln -s '/usr/bin/$EDITOR' $(which $EDITOR) after a fresh install, so I have a valid executable on the path called $EDITOR.
  
  Of course, then I have to make sure to add export EDITOR=\$EDITOR to my .bashrc. (Obviously.)

I started on Unix systems using Vim, so I find Nano to be the confusing editor. A Vim install is one of the first things I do on a new server.

I'll say that I find easier to exit vim that to exit nano.

I don't know what ^ means. I just start pressing special keys until it doesn't the thing

CTRL

That's like the picture of a normal dude with Nano, a large Vim dude, a larger buff Emacs dude and an ever larger massive Ed dude.

eh the emacs folks are just chilling in a corner somewhere. Maybe in the old folks home together with the ed users
Don't forget the joe user in the corner wearing a trench coat with a bomb strapped to his chest wired to a dead man's switch.
Ed is like Skynet itself.
Do people still use ed unironically outside of scripting context?
- Unironically? Maybe not. But using something ironically is still using it.

I like nano tho it has some strange shortcuts

micro has some improvements and default shortcuts that are much closer to common GUI text editors

https://micro-editor.github.io/
- oohh that is nice, I think I'll swap my nano to that.

Nano isn't even that simple. Ctrl+X to quit? I guess if you use phonetic sounds to figure out how to exit a program. At least Vim uses the idea of "use what the words start with."

I personally use micro in the terminal, and Kate if I want a GUI to write. Vim and Emacs are fine for those who want it, I have no stakes in the editor wars beyond "I just want my program to do what I want, and I want it to be simple to learn."

Nano has a cheat sheet at the bottom of the screen at all times
- Meanwhile I can just use the same shortcuts every other program made in the last 40 years uses. Ctrl+Q to quit, Ctrl+S to save, Ctrl+Z for undo. If I wanted to consult a cheatsheet to relearn keyboard shortcuts, I'll use vim and emacs.

There's always ed for masochists.

Isn't this supposed to be VIM vs Emac? What's is there point to be programming in the terminal anyway? Nano is good to fix some config files while your are in there, but if I needed to do real programming I'll be finding something that works in the GUI.

Did you just say GUI?

More like ewwwie.
- Its GNUI
Efficiency.

There's 0 chance if you have to pick up your mouse that you can keep up with a Unix gray beard.

That's just editing, if they're from the emacs era there might be nothing you can do with text faster across their whole system.

I like vscode as a entry point, but if you care to get faster learning just vim motions and sys utils alone is going to cut time from the process.
- Oh it's about speed. What's the one that get your brain to be faster at programming? I use 4 fingers typing and am still typing much faster than I can think.
supposed to be VIM vs Emac?

30 years ago it was vi vs everything. I don't see it changed today.

Micro for the win

No, Micro for the linux
- Nah, win can have it.

Easy is relative. What are you trying to do? Replace a value in an yaml file? Then nano is easier. Trying to refactor a business critical perl/brainfuck polyglot script in production? Then you probably want to use vim (or emacs if you are one of those people)

Replacing a value in a config file is still easier in vim due to e.g. ciw or ci" being a thing.
Walk someone else through editing a config file on the command-line over screenshare? Nano. Omg nano is your friend.
Honestly, roll back to previous release for production and use best IDE your developers are used to on their local machines, test the fix in a non production environment then release to prod. When is editing business critical scripts in production really needed?
- It was a joke to make the point that vim can be the easiest tool to use if you are trying to do a complex task.

The problem I had with nano is that, for the time being, it was supposed to be easy to use. With that in account I always get lost when saving a file and closing the thing because one's used to doing something else with Ctrl+O and Ctrl+X.

Whereas with Vim (and Neovim for a little while, and now with Vis) I knew it had a steep learning curve from the start so I always had it in mind. And all the funny stories about quitting vim.

they've changed those bindings now, Ctrl+S, Ctrl+X, Ctrl+V, and Ctrl+C all do what you think they do
- Great, now the next time I use nano I surely will forget about this and get frustrated when trying to save a file with Ctrl+O
- I'm thinking Ctrl+C quits and Ctrl+S is scroll lock is that correct?
I mean quitting vim isn't hard you just reset the computer.
The problem with using nano for years is that I now try using nano shortcuts in other programs. Random new windows opening is confusing, until you figure out Ctrl+o isn't save in that program. Then it's just annoying because you still have your inappropriate muscle memory.

The Holy Trinity: VIM, Arch, and Rust

That's a weird way to spell Vim, Arch, and C
- Seems you have a little typo, Emacs, Arch, and C

idk man, vims pretty chill, it even has a tutor in it already, what more could you want?

it even has a tutor

Yes, people are just lazy. I remember when I invented a new login screen and was told it was "difficult", "confusing" and "took some getting used to".

It even came with a free 100-page manual and a 4-hour master class. Some people, I tell you!

^This is meant more as a joke than an actual critique, even if it kind of reflects my thoughts. But ultimatly, I thought it was a funny bit.^
A text editor that doesn't need a tutor because the interface is intuitive enough that someone who has been using text editors (as a concept) for years can more or less instantly pick it up and start working without needing a tutorial to simply edit a config file.
- a text editor that has a tutor because it's been around for so long and it's had so many years to establish itself with an outside control interface that's quite literally about as optimal as it can be. Vim basically allows you to never move your hands away from the homerow keys, even when navigating and doing bulk edits. The sheer amount of gained speed and productivity you get from this combined with the amount of times you'll have to deal with text editing throughout your life is probably going to outweight any potential learned annoyances.
A text editor that doesn’t assume that the keys on my keyboard are in the same order as yours.
- I remember looking up how to use Colemak with vim, and the advice was:
  
  Change the mappings so the position is the same, but it has the downside that every tutorial won't match.
  
  Keep the mappings and do awkward stretches for common functions like up and down.
  
  So I just gave up and moved on.
- that is a potential problem, though im sure there's a vim user somewhere that's fixed it with a bind set.
One that's intuitive and doesn't require a cheat sheet or what I like to call fingular contortionism discovery.

I just use this:

#!/bin/bash

keep_generating=1
while [[ $keep_generating == 1 ]]; do
    dd if=/dev/random of=$1 bs=1 count=$2 status=none
    echo Contents of $1 are:
    cat $1
    echo
    read -p "Try generating again? " -s -n1 answer
    while true; do
        case $answer in
            [Yy] )
                echo
                break
                ;;
            [Nn] )
                keep_generating=0
                break
                ;;
            *)
        esac
        read -s -n1 answer
    done
done

Just ask if it's correct. If not destroy the universe. Only The correct will survive, it's O(1)
- What if there is no correct answer?

Emacs users laughing at VIM users.

Emacs - A pretty good OS you can use as a text editor.

And to counter the old saying of it lacking a decent editor, there's always evil-mode.

is there not a single other person who uses helix?

WTF is helix?
- https://helix-editor.com/
  
  essentially a terminal modal editor (like vim), but instead of specifying the action to perform then what to perform the action on (like "yank 3 lines"), in helix you select first, then perform actions on the selection (like "these 3 lines, i want them yanked"). it's slightly better (according to others) because you get to see what you're going to change in the file so you don't accidentally delete 5 lines instead of deleting 4.
  
  on top of that many features are builtin, like tree-sitter and lsp support, so you don't have to spend 5 hours looking for cool plugins and configuring everything to get started (my config file is only 50 lines of toml).
  
  the downside is that there isn't support for plugins (yet), but there's already things like a file picker, more than 100 themes etc.
I gave it serious consideration when the death of Atom was announced and I was unsure where to move on to.

Looks like in the meantime a lot has been done (as far as I remember, TreeSitter and LSP weren't built in back then...? Not sure though), but the lack of a plugin system is still killing it for me.

TBH it looks like it has 75% of the features you want from a codeditor, which is much more than the use-case for Nano, but no way to go the remaining 25% of the way.
- the death of Atom
  
  I'm still in mourning.
Helix's editing model is so much better than vim's. I would probably use it if it was be closer to a drop-in replacement for vim. I really hope this neovide issue gains some traction because I don't think I can daily drive anything that isn't as smooth as neovide again.
- I simply have too much vim config and muscle memory to ever leave vim
  
  I'm trapped in a prison of my own making!
Well I tried! I ended up using micro though
I like helix

modal editing can be fun. it is a weird skill like driving a manual transmission.

that said driving a manual transmission in stop and go traffic on a hot day is a lot like editing in vi sometimes.

Unless you're European. Then driving manual is considered basic life skill like riding a bike.

Micro is where its @ <3

For vim I had to config or install something just to be able to COPY something to use outside vim, how backwards is that? Isn't this the most standard feature one can expect to work as default?

You mean you couldn't copy some text from vim and paste it into another application? if yes, what did you have to install/configure for that? I've never had any issues copy paste from/to vim, console/GUI windows/Unix.
- Sadly I don't remember. Sometimes it comes preinstalled, sometimes not, depending on OS or something. (Maybe Manjaro gnome). I could copy and paste inside of vim, but not to/from outside vim.
it actually does work by default, you just probably missed how to do it in the help pages in vim. For those curious, the system clipboard is its own named register in vim (:help registers to learn more) and can be accessed with either “* or “+ depending on your how your system is configured.

To copy a line: ”*yy or ”+yy

To paste a line: ”*p or ”+p
- So I need to dive into the manual to do something as basic and universal as "copy and paste"? Why not make it Ctrl+shift+c or have it shown in the info text when pressing this almost universally accepted keypairs? Or at least make it somewhat similar to this. I find it bonkers why some programs decide to just have radically different shortcuts or defaults, the complete opposite of what feels intuitive. Same with the design of some doors that need actual SIGNS on them to tell you which direction they open. Just bad design choice.
  
  Edit: just remembered. Same story with tmux. Want to copy something? Surprise, it's not anything you expect it to be. Some ctrl+b + [ or some shit

Me on Micro

100% Micro. Unless you’re only - and mean ONLY - living in the terminal, why would you want all your desktop and terminal shortcuts different from one another?!
- Fwiw, you can change the shortcuts for nano in your ~/.nanorc. Most of mine are the same as standard desktop editors, except undo is Ctrl+U because Ctrl+Z is commonly bound to suspend, and quit is Alt+Q instead of Ctrl+Q because in browser window terminals (e.g. Unraid) Ctrl+Q usually closes the whole browser (oof).

Nano is my "daily drive", but I'd use vim as well -- takes a couple seconds to search for "how to type in linux vim" and "how to save a file in linux vim" anyways. :^)

I know i and :wq and that's all I ever plan on learning
- Not even Basic Command-Count-motion like c3w aka change 3 words after cursor, or d3b delete 3 words before the cursor?
  
  To that, you add the D aka delete command C for change Y for yank (copy)
  
  So yy to yank line, or dd to delete line.
  
  Also p for paste
  
  Also, i sends you before the cursor, a sends you after. Capital I is insert at beginning of line, Capital A is insert at end of line (append).
  
  I terms of motions and moving around, you need: hjkl, C-d and C-u (half page jumps down and up), and within the line: 0 or ^ for beginning of line, $ for end (taken from regex), w for moving by word forwards, b for moving by word backwards. That's pretty much all you need imo. There is also t and f. Where t goes forwards (think 'till aka until). Like dtc delete until the c character. F is the same but goes backwards in the line rather than forwards. Remember you can use these with xommands, so d$ deletes until the end of the line. Or "dt." deletes till the "." so.... yeahI know there's more, but that's all you need for Normal and Insert mode imo.
  
  For Visual mode, you only need to know how the Visual modes work. Visual (v), Visual Line (Shift-v) and Visual Block (Ctrl-V).
  
  Also, for visual mode, it might be helpful to learn how to use V-Block to comment out multiple lines at once. Can't be bothered to go into it.
  
  But I'd argue that's all there is to learn about vim keys in terms of getting work done.

I started on Emacs and then didn't use it for a few years and forgot everything so now I'm stuck on Nano. But that's fine because nano does everything I want it to do.

kwrite and gedit friends rise up :)

On KDE, there's also Kate. They used to be totally different apps, but these days, KWrite is a simplified version of Kate. They both use the same text editor component, but Kate adds more IDE-like features.
- true but i dont like how they are forced togther so i use featherpad
How do you use these when you are connecting via SSH? You enable X forwarding?

It's fine when you have a graphical environment, but what do you do when you dont have one?
- Using X forwarding would require you to install big chunks of GNOME or KDE on the server. A better approach is to mount the remote server over SFTP then use KWrite, gedit, whatever, directly on your desktop.
- A similar argument is what finally caused the value of the vi family of editors to click in my brain:
  
  They are designed to be fully functional over even the shittiest possible* remote connection. You can't always count on ctrl, alt, or even the arrow keys being transmitted in a way that is understood by the remote machine.
  
  *Well, I guess the worst possible terminal would be something like an actual teletype, and in that case you'd probably want to fall back to ed or its descendants. To save paper, if nothing else.
- ohh yeahh then nano
- In any KDE app you can connect with SFTP in the open file dialog. Just type sftp://user@server/path and you can browse/open/edit files the remote server. ssh keys+agent make things a lot easier here obviously.

Ed users entered the chat

I spent the weekend failing to make my civ mods work, with a thousand lines of notes.. 2/3 in, I think "damnit blazeknave. You spend months perfecting this stupid fucking obsidian setup, and you've been here in notepad+ like a fucking jabroni."

I do the same all the time with anytype.

I dropped notes into sublime and then go back and put them neatly into any type. I don't really know why I do it either It takes any type a total of three or four seconds to start up and I have to enter in a passcode. But I only have to do it once. I guess I do have to think about where I'm going to put the document and making sure that it's tagged correctly, it's a lot easier just a scribble something into a random text window to forget about for a decade.
- You mean my 6k Gmail drafts? 😭
  
  I started doing paper pads everywhere and trying to log at end of day.

Imagine using Nano or Vim; when you could be using Cat and Echo.

/s

Emacs

Hey now we don't denigrate vim and nano users. For the nano users, denigrate means to put down.
- and sometimes you just need a text editor, not an entire thesaurus

Greybeard here. I can use vi, emacs, nano, etc. and use whatever is available if it suits the job. For many years I did dev in emacs on my computers and on other systems used vi for quick edits. Currently on my own laptop I have micro as default term editor now. For Rust development - code, though I have hopes for Lapce.

They're all just tools and so are people who get tribal about things.

Butterfly gang

Worst is when installing a new distro(usually in a vm ) and it defaults to nano and for some weird reason no vi of any sort is installed. I hated nano. Last time I intentionally used something like nano was the 90s with pine I think.

What is there to hate? I don't really understand. It does what it says on the package, and seems to do it pretty well. At least with respect to making small and quick edits to config files in the command line.
- My fingers don’t speak it is the problem.

There is always the Joe editor, if you like good ol' Wordstar. :)

I've been known to watch a fight video there every now and again, yes.

Get'er Robbie she's under the desk!

If I'm doing quick txt editing nano is great and what I know I can't figure vim out for the live of me

On my laptop, I update my bashrc on Excel, in Wine, then export it as a PDF, OCR to .md, Pandoc it to an .Org, and then finally, write it down on paper and re-type it on my phone's Termux's Emacs instance, then TRAMP it to my PC, in the other room.

I use biebian, btw.

Its lighter weight

Memes like this make me glad I only usd Linux at work. You don’t get this petty micromanaging shit between windows users.

My problem with those are that I always manage to get lost on where the program has its focus/what kind of instruction is expecting. And while trying to go back to normal I end up messing it more and more. Maybe some day I will get there, but it is still not the day.

gedit supremacy

Nano is notepad, but with worse mouse integration. It's Vim/Emacs without any of the features. It's the worst of both worlds

If you want ease, just use a GUI notepad. If you want performance boosts, suck it up and learn Emacs or Neovim

Why would you use a mouse in a console editor? Most of the time, if you're using Nano, it's because you're not in a GUI environment.
Heaven forbid I want to use an intuitive, simple, terminal based text editor when I ssh into one of my boxes.

But here's the real kicker. Why do people like you give two shits what text editor other people use?
What if you want ease on a terminal?

Vim is way easier tho

The first time I found myself in nano was when testing a distro fifteenor twenty years ago. I had to edit some files and it was the only available editor. The damn thing was a horror to use. I still have no idea who it caters to. I haven't had to use it since though.

Dunno what you used, but nano is literally a text editor that may be simple simple but it just works. Shortcuts are shown to the user, buttons work like you expect them to (arrow keys, ESC, shift, etc)

With vim you open it and if you haven't read 5pages of doc you won't even be able to close it again. I see that its useful for power users, but for casuals who just want to edit a config once in a while nano is absolutely the way to go imho
- It's not that simplle or user friendly when none of the usual shortcuts work. C-a did something completely unexpected.

isn't there a separate instance for memes?

Ohh look! a sad scripter editing his tiny little script on a terminal window. How cute.

Ugh, I swear vi and it's derivatives are the absolute worse text editors going. There may have been reasons thirty or forty years ago, but now it's just complexity and a weird ui for the sake of it

I use VS Code on the desktop nowadays, but vi will always be my editor of choice in a terminal. Many of the reasons it was powerful and ubiquitous 30 years ago are still valid, so it’s still powerful and ubiquitous. And I’ve been using it for thirty years, so why would I switch to a training-wheels editor?
- Because you want to get out of your Stockholm syndrome?

Vim actually IS easy to use once you get the hang of it, plus more comfortable and efficient.

Nanos just an excuse for lazyness, cmv.

stop using nano, if you want a non modal editor use vim -y