as I'm going through the process of learning vim, I'm discovering newfound powers. one of them being to execute commands from vim itself.
below examples might better explain some of them:
want to see what files are in current directory? enter command mode(by typing :) and follow it by a bang(!). then do ls like you'd do in a terminal and press enter. this is not limited to just ls. you can enter any command that you can enter in terminal. for example: :! uname --operating-system (which will output GNU/Linux :))
so you want to quickly save just a certain part of your file into another file? just select everything you need by entering visual mode(v) and do :w filename(actual command you'll see would be '<,'>:w filename). verify it using 1.(i.e., :! cat filename.
want to quickly paste another file into current one? do :r filename. it'll paste its contents below your cursor.
or maybe you want to paste results of a command? do :r !ls *.png.
I love vim, but it wasn't always like this. When I was a Linux newbie one of the things that irritated me most is that tutorials aimed at beginners told readers to use vim, without explaining how to maneuver it. People, if you write tutorials aimed at beginners please use nano, even if it's not your preferred text editor.
The first time I opened vim (it was probably just vi at the time) I couldn't exit it and had to shut down the computer by holding down the power button (!) to regain control of the machine. It took a while before I tried it again. Ultimately nano felt like it was for kids and emacs felt like an even worse option than vi so I memorized a few sequences, eg :q!, :wq, how to enter the insert mode and how to exit it and simple edit commands like dd and x and this gave me enough proficiency to get by.
Most all the terminal commands require prior study before they become easy to use. Its because Unix was created by engineers rather than by ui/ux design professionals.
In Linux terminals, you probably could have pressed Alt+F2 or Ctrl+Alt+F2 (F2 could be other F-keys) and log in on a second terminal to recover (by reading the manual or killing it). Also, if bash already had job control back then Ctrl+Z would have suspended vi/vim to the background.
I'm writing this, so people try it and maybe remember it, if they get stuck in some program. Doesn't have to be vi. Maybe you just launched a long dd command and don't want to end it, but want to look something up. These hints may help then.
It’s because Unix was created by engineers rather than by ui/ux design professionals.
This is somewhat disingenuous. Unix terminal is one of the most ergonomic tools out there. It is not “designed by engineers”, it is engineered for a purpose with user training in mind.
Ergonomics is engineering. UI/UX design is engineering. UX designer that doesn’t apply engineering method is called an artist.
i agree with your request. vim used to scare me first.
as a side note: one of the reasons I believe as to why vscode grew in popularity was due to it lowering the barrier to just open up the editor and use it right away(with plugin system and a nice GUI). it is something vim by default doesn't do.
What’s wrong with nano? I love nano. As a general thing I love Linux programs that are terminal based but also have a decent UI. Neomutt comes to mind for email.
There’s nothing wrong with nano, it’s a simple text editor while vim is much more versatile and aimed towards that are already accustomed to terminal software.
I will not make vim my sweet as it is optimized for us keyboard. Most of the shortcuts are awful in my native (Finnish) layout. As much of a heretic I am, there is a place for mouse and windowing display managers.
What I do miss from the Redmont dystopia is Notepad++. Can do anything, can be explained over the phone.
This is the duality of Linux. Linux is an easy OS that's extremely customizable and everyone should use it. But also you may have to choke out your PC to exit the text editor.
Did yall know that Notepad has tabs now? So does explorer!
I'm personally a kakoune guy now. I used vim for over a decade, but kakoune just makes much more sense to me. And I thought vim made a lot of sense, too.
I was forced to learn the vim basics. Mainly because I really started with dd-wrt, which I used on my Linksys WRT54GL.
The image was too small to package anything fancy in it, like nano or something, but vi (or vim, I forget) was included. So when I needed to check something over ssh at the command prompt, vim was my only choice.
My skills in vim have not expanded beyond the basics. Getting into edit mode, exciting edit mode, saving, quitting.... Mostly.
I don't spend a lot of time editing files in the CLI, so I haven't needed any more than I already know. Now, when faced with a Linux cli, and needing to check/edit the contents of a file, my go to, is vim. It's pretty much on every system, and it works perfectly fine for what I need to do 99.99% of the time. I like vim, it's been there for me through thick and thin, and helped me out of some serious jams. I won't hate on nano (or any other cli file editor), they all have their pros and cons.
Or I can just NOT waste my life and my sanity trying to remember all that BS and just use a mouse and a GUI editor. I have no need to feel like a hackerman.
I agree that remembering all these commands is a hassle, and so do nvim devs. that's why they recommend not to learn the commands1. these will become your second habit if used enough number of times. just like Ctrl+c/v.
1: from :Tutor in nvim:
NOTE: As you go through this tutorial, do not try to memorize everything, your Neovim vocabulary will expand with usage. Consider returning to this tutorial periodically for a refresher.
also, even if you don't want to use a terminal-based editor, I'd recommended you to give this talk from Bram Moolenaar(creator of vim) a watch. not the whole talk, just a few first minutes. you can even use YouTube chapters to skim through.
On one hand, yes. On the other hand, you don't need all the keybinds, just remember the useful ones!
Want to delete a single word? Esc to enter command mode, d i w to delete the word you're on, I to begin typing again.
Everything between two of any char, usually parenthesis or quotes? Same process but d i {char} so something like "what are (you doing senpai)" can be made "what are ()" with just a few very quick keystrokes.
Delete to end of line? D.
Copy a whole line? yy (or Y for the rest of the line after cursor). Any time you do dd to delete a full line (or D for the rest of the line, or any other delete action) the contents are also copied so you can paste them again somewhere else.
Can you do anything with vim that you can't do with a GUI + moise? Technically no - but with vim you can do things significantly faster. There is an initial learning curve to get used to basic keybinds and the 2 modes, but it's well worth it, and not using the mouse is intoxicatingly faster and more fun.
I highly recommend doom emacs over vanilla vim- all the power of emacs, but with vim keybinds and a lot of other QOL features. There isn't much that isn't already built into vanilla emacs, much less doom emacs, and even less that can't be added with some packages that you can install from in the app. Web browser? Eww, and you even can use your vim keybinds in it. Doesn't render everything great graphics wise, but it's perfect for looking up documentation if you're lazy. Email? Built in baby. Git? Magit. Notes? Embrace the one true note format, org files and org-roam. File explorer? Dired right in baby. Terminal? Space + o + {t, T} for a terminal in its own buffer for all your terminal pleasures.
I also always install neovim as a backup, it was my favorite vim client for a while. It's useful to be able to use it for basic editing if I'm already trolling around in a terminal such as quick edits to docker-compose files before rerunning them
Honestly I felt the same way for a long time, until I decided to just learn the motions. Now I couldn't go back.
The combination of actions and motions makes it incredibly fast to edit code - Imagine you have a strong in double quotes that you want to change the double quotes to single quotes. There's a plugin called vim-surround that combines with the basic motions and with my cursor before or within the strong, I can just type cs"' and it's done.
Want to copy everything within a pair of parentheses? yi) ... So many things like that.
Even for editing things like HTML, `cst delete surrounding tag. That will remove the tag around some content without changing the content.
(Neo)vim is incredibly important to my workflow these days and it feels like I write and edit code at the speed of thought.
The good thing about vim or Emacs is that when you know the shortcuts they are so much faster to use than mouse and menu editors (though Emacs has a menu, and supports mouse, which smooths the learning curve)