Skip to content

Neovim comment #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
teacherc wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Neovim comment #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions 2021/why-use-emacs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,8 @@ Want to make a comment? Hit '.' to edit this page. Then submit a pull request.
### Emacs -> Vim -> VSCode
Roni here! I started out using Emacs in January 2000 (the same year I started using Linux). Then, when I started at Kitware in 2012, I thought I'd like a change and switched over to Vim. Now it's 2021 and all the cool kids are using VSCode, so I finally took the plunge and discovered that its integrated LSP support is pretty sweet. I'm feeling that slow slide away from Vim now, even though it wrecks some of my "old man" appeal.

### VSCode --> Neovim (AstroNvim config)
When I first started learning how to code, I used VSCode because it's mechanics mirror a word processor. I didn't want to learn how to use an editor on top of learning Python, design patterns, Git, and other important skills and concepts. Within the first few hours of my first professional software engineering role, I decided to use Neovim. I saw all of the senior engineers using it and marvelled at how quickly they could edit and insert text. At first, I was going to commit to learning VSCode features and shortcuts. I realized that these shortcuts would still require me to use my mouse more often than I would like. Also, there is no underlying grammar behind the shortcuts. I've enjoyed learning Vim motions because there is an underlying grammar behind them. This means that I can infer shortcuts based on previous motions and actions I've learned. Each time I find myself doing something slowly or with a mouse, I Google it and learn how to speed up my work. There have been some annoying moments, and I'm not a Vim expert yet, but using Vim has helped me drop my mouse usage and spend more time in the terminal. As for the features that make VSCode great, I'm using an [AstroNvim](https://astronvim.com/) config that gives me access to an LSP, terminal windows within Vim, a great fuzzyfinder, package management, etc. I feel like I have a [PDE](https://www.youtube.com/watch?v=QMVIJhC9Veg) instead of an IDE.



Expand Down