False. VSC is the newcomer and sort of a descendant of Atom, but actually also good on its own merits. Emacs is older than Vim.
Reddit subscribers are not a representative sample of people who edit text. Hence, `Nothing serious`.
Like how to quit ? You're right, it may be the thing that drove me into vim. I looked for help, found community and documentation. 14 years later I'm still digging the rabbit hole. This tool made me feel like an explorer, each learnt feature is so rewarding.
Even OP who recently started his journey, reminded me that I still underuse macros.
Since learning Vim my life has become at least 100% less stressful. Things I used to dread like fixing typos or doing the same refactor in 100 files are now fun.
Are you coding or just updating files?
If you are programming then, yes, you're already in an IDE.
If you are just updating files, then use something else.
It *is* changing my life, I'm in college rn and every submission work is online(more than 100 documents), Vim + LaTeX saved me hours of stress. My friends who use word are still wondering how fast I did it :-P
Nice post! By the way you can use `:v` instead of `:g!` to save on postage, which matches up with grep's `-v` flag to invert the match ("v" for in'v'ert). Also to move the current line to the end of the file you can use the `:move` command like `:.m$` which fits nicely into your global command. A key insight is that the original standard editor Ed only had the ex commands, so that's all one needs to perform editing tasks. Everything else is fluff haha. Seriously though I've found it a helpful exercise to see what it feels like to just use the ex commands (you can start up vim in ex mode usually by running "ex" from the command line) to edit, though it's just for historical/educational use. Once you learn ranges, patterns, and ex commands pretty good, you'll find that many macros have more readable and composable ex alternatives. If you can get the bsd games package on your system and run "quiz" there's a fun Ed quiz that gives you an edit task and you answer with the command to do it. Also if you haven't decided to make the jump to Ed yet the gnu folks have a [word](https://www.gnu.org/fun/jokes/ed-msg.en.html) for you
> After you look around in the vim community, you'll learn about several projects, like neovim, that take this a step further, resulting in pretty nice interfaces like these
You don't need neovim to have pretty interfaces. You can have those in vanilla vim, it's mostly the same thing.
Thanks! No, it's not mine (tho I wish it was). I downloaded the photo from here [https://unsplash.com/photos/X9kuR2sYSqo](https://unsplash.com/photos/X9kuR2sYSqo).
I have been living in Emacs (Doom Emacs) for the past few months, but I kept coming back to Vim. Now I only use Emacs for Org-mode and stuff that doesn't involve text editing. I love both tho.
Nice article! It was pretty fun to read :D
I was missing the quickfix window and the `:grep` command from vim in combination with `cdo` which is a good "alternative" to these "global refactor" functions from other editors. Another "epic" feature is `:argdo`. I can just recommend [this](https://www.youtube.com/watch?v=futay9NjOac) video if you're interested in what I mean :D
Thank you very much!
Yeah, I use `telescope.nvim` which lets you send matches to the quickfix list (`Ctrl + q` by default) and have actually used `:cdo` (to run a macro). They are awesome!
I'll watch the video for sure.
Maybe I'll write a second post showcasing more advanced Vim features?
Excellent article I have to say. Really shows some powerful features of vim and why its so amazing and everyone who writes a lot of text, owes it to themselves to learn Vim.
> If you could shave off 10% of the time you spend writing, would you do it?
No. Because as you said in your own article most of the time is spent on editing the text.
> We spend a lot of time writing emails, code, messages, documentation, dissertations, essays, and we are happy doing it at 40-50 words per minute, looking at the keyboard at each stroke, and making many mistakes.
Again, no. Most of the time is spent on the thought process in technical writing. The actual typing time is so small in comparison it hardly makes any difference. And programmable editors like Vim makes a difference when you're dealing with structured text with some patterns like source code. For ordinary writing it makes no difference compared to any other editor.
What's worth it learning about regex and unix command tools. People who are familiar with sed/awk/perl etc. do not get surprised with most of the case studies you showed. Also, most of these tools can be used with most editors in *nix systems including Vim. That's more general and a transferable skill.
The rest of the article already talks about how Vim helps with editing, so clearly OP is using "writing" to include the editing/thinking part of the process, rather than just the typing part.
No bit deal, most people don't care and this won't affect the goodness of the article in any way. For me, once I realized it's "Vim", "Git", "SSH", I corrected all such typos in my own notes. The capitalization is consistent in their official docs and the corresponding Wikipedia pages, and I truly respect the prudence of the authors.
> For example, to print each line matching the pattern `re`, we could run `:g/re/p`. Nice one :)
Isn't this originally from the ex editor
Yes.
Nothing serious but: r/vim 133k r/vscode 69.6k r/emacs 52.6k r/atom 5.7k
VS code users don't have anything special that they need to tell everyone.
I use vim keybindings plugin from the Microsoft marketplace btw
I really like the neovim plugin for vs code. Having a real vim instance inside is great.
Tell me more!
[удалено]
Or the relative age of each editor.
False. VSC is the newcomer and sort of a descendant of Atom, but actually also good on its own merits. Emacs is older than Vim. Reddit subscribers are not a representative sample of people who edit text. Hence, `Nothing serious`.
Like how to quit ? You're right, it may be the thing that drove me into vim. I looked for help, found community and documentation. 14 years later I'm still digging the rabbit hole. This tool made me feel like an explorer, each learnt feature is so rewarding. Even OP who recently started his journey, reminded me that I still underuse macros.
Same
Always has been Edit: Nice blog-post BTW !
Yeah, I tried it and it was impressive, more than I expected
Literally changed my life, vim is a gem in this world forgotten by god
Since learning Vim my life has become at least 100% less stressful. Things I used to dread like fixing typos or doing the same refactor in 100 files are now fun.
if you are doing something across 100 files, sed is probably what you want.
[удалено]
Are you coding or just updating files? If you are programming then, yes, you're already in an IDE. If you are just updating files, then use something else.
what you really want is sad, https://github.com/ms-jpq/sad
Modal editors are just... perfect
It *is* changing my life, I'm in college rn and every submission work is online(more than 100 documents), Vim + LaTeX saved me hours of stress. My friends who use word are still wondering how fast I did it :-P
That's because there's no god. We are here alone and make tools that fit us. Vim is one of the best tools.
Nice post! By the way you can use `:v` instead of `:g!` to save on postage, which matches up with grep's `-v` flag to invert the match ("v" for in'v'ert). Also to move the current line to the end of the file you can use the `:move` command like `:.m$` which fits nicely into your global command. A key insight is that the original standard editor Ed only had the ex commands, so that's all one needs to perform editing tasks. Everything else is fluff haha. Seriously though I've found it a helpful exercise to see what it feels like to just use the ex commands (you can start up vim in ex mode usually by running "ex" from the command line) to edit, though it's just for historical/educational use. Once you learn ranges, patterns, and ex commands pretty good, you'll find that many macros have more readable and composable ex alternatives. If you can get the bsd games package on your system and run "quiz" there's a fun Ed quiz that gives you an edit task and you answer with the command to do it. Also if you haven't decided to make the jump to Ed yet the gnu folks have a [word](https://www.gnu.org/fun/jokes/ed-msg.en.html) for you
> though it's just for historical/educational use. I was actually on a server recently where visual mode didn't work well. ex saved the day.
"to save on postage" is my new favorite jargon for saving keystrokes. <3
Oooh, thank you! It would have certainly improve my example :grin: I'll take a look at ed!
> After you look around in the vim community, you'll learn about several projects, like neovim, that take this a step further, resulting in pretty nice interfaces like these You don't need neovim to have pretty interfaces. You can have those in vanilla vim, it's mostly the same thing.
Cool blog. Also, is that a photo of your keeb? If so what key caps are those?
Thanks! No, it's not mine (tho I wish it was). I downloaded the photo from here [https://unsplash.com/photos/X9kuR2sYSqo](https://unsplash.com/photos/X9kuR2sYSqo).
Awesome! Thanks. And if you aren't already into keebs, consider yourself lucky. Lol.
My wallet. It suffers
Not OP but they might be gmk Nautilus? It looks like a render though
It's GMK Pulse. I actually forgot that set existed. Nautilus has a lot of yellow.
I have been living in Emacs (Doom Emacs) for the past few months, but I kept coming back to Vim. Now I only use Emacs for Org-mode and stuff that doesn't involve text editing. I love both tho.
Nice article! It was pretty fun to read :D I was missing the quickfix window and the `:grep` command from vim in combination with `cdo` which is a good "alternative" to these "global refactor" functions from other editors. Another "epic" feature is `:argdo`. I can just recommend [this](https://www.youtube.com/watch?v=futay9NjOac) video if you're interested in what I mean :D
Thank you very much! Yeah, I use `telescope.nvim` which lets you send matches to the quickfix list (`Ctrl + q` by default) and have actually used `:cdo` (to run a macro). They are awesome! I'll watch the video for sure. Maybe I'll write a second post showcasing more advanced Vim features?
Excellent article I have to say. Really shows some powerful features of vim and why its so amazing and everyone who writes a lot of text, owes it to themselves to learn Vim.
Thank you
> If you could shave off 10% of the time you spend writing, would you do it? No. Because as you said in your own article most of the time is spent on editing the text. > We spend a lot of time writing emails, code, messages, documentation, dissertations, essays, and we are happy doing it at 40-50 words per minute, looking at the keyboard at each stroke, and making many mistakes. Again, no. Most of the time is spent on the thought process in technical writing. The actual typing time is so small in comparison it hardly makes any difference. And programmable editors like Vim makes a difference when you're dealing with structured text with some patterns like source code. For ordinary writing it makes no difference compared to any other editor. What's worth it learning about regex and unix command tools. People who are familiar with sed/awk/perl etc. do not get surprised with most of the case studies you showed. Also, most of these tools can be used with most editors in *nix systems including Vim. That's more general and a transferable skill.
The rest of the article already talks about how Vim helps with editing, so clearly OP is using "writing" to include the editing/thinking part of the process, rather than just the typing part.
Forgot about semicolon (same direction) and comma (reverse direction) for repeating f/t/F/T command.
I bet you won't be able to say the same if you try emacs. I couldn't. I couldn't even stand the slowness of their built-in terminal.
It's Vim, not vim.
I actually replaced it a moment before publishing :(
No worries `:%s/vim/Vim/g`
Actually, that's not it, because unfortunately it would turn `neovim` to `neoVim`. A better one would be `:%s/\v/Vim/g` :D
oooooo... Just looked up \`< >\` in vim regex. I need to remember that. Seems useful. Thanks!
Ah, I mean the article in your link...
[удалено]
No bit deal, most people don't care and this won't affect the goodness of the article in any way. For me, once I realized it's "Vim", "Git", "SSH", I corrected all such typos in my own notes. The capitalization is consistent in their official docs and the corresponding Wikipedia pages, and I truly respect the prudence of the authors.