Wasn’t ChrisAtMachine the guy who had a Neovim from scratch series? Unfortunately he scrapped it a bit, and now just distributes a fully baked LunarVim.
@@ThePrimeTimeagen but that's the truth. You are 40 if you are 40. I knew a guy in his 20s who used vim for almost everything so editor doesn't confirm it!
12:44 would be great if you could show how you structure your code to achieve this. I know a bunch of people say "well separate your ins and outs from your logic" and stuff like that but having a real tangible example would be great
It took me like a week to properly configure nvim with lazy, lsp, treesitter, telescope and other desired plugins. The configuration I'll probably be happy about for the next couple of years. Knowing what every line does and being able to provide any possible customization I might want, where everything is set up exactly for your needs. This feeling is quite impossible to get with any other editor.
when you make a vim config, it's all one configuration and so you can know what every line of your config does. kind of like settings.json + extensions.json + keybindings.json in vscode, but at the end of the day you still don't know how vscode works it's all.. magic @@MrAbrazildo
Being very old, I use vi. Well, that is pointed to neovim now. I'm on the keyboard; Fingers do that. ee gets me file search hm gets me harpoon It also compiles fine on a Raspberry Pi arm6 - 0.9.1 (not that I code on that, I cross compile, I compile it to make sure system is good)
Actually they are Vi and Ex motions and commands, Vim was later developed to be an improved Vi. And if I am not wrong, Vi was even a kind of an extension to Ex, which was also based on some kind of older tool if I am right with that too. Maybe some older Unix gurus are reading this and can add more information here.
I don't think ex was a visual editor with motion commands, but some of the line edit commands, like in the s/ and "sed" type syntax, resemble the vi commands. Vi is the visual version of ex
@@vikingthedude Anything and everything related to editing text outside of development. I even have my file binding for txt files set to open vim in a CLI, I just don't write code using vim.
Kickstart is magic, I started with it. It is the bare minimum to understand how vim works without a ton of overwhelming features. Once I got the basics I replaced it with my custom version and boom
I set up NeoVim using Kickstart today after re-installing Linux. After I added some of prime's suggested keybinds and harpoon, it's pretty much perfect. I put my edits on a fork and now I can get up and running in like 15 seconds 😁
fr the main issue i had with neovim "distro"s is that over a certain level of customization you need to look into its implementation specific, outside of how im supposed to configure it. as those distros have quite complicated implementation, its hard to do so, while kickstart.nvim exactly solves that as its (almost) a single lua file with about 300-ish lines of code excluding comments
I had sone downtime last w/e so gave neovim a shot. Took a long afternoon to set it up. C/C++ dev with fairly large projects. Used VSCode, currently using CLion. Conclusion, I kinda get the keyboard speed thing. The tooling though isn't a patch on CLion (or VSCode) for large scale C/C++ dev, profiling and debugging. Customising and config is a PITA especially when you just want to get wotk done. Pain points on underdeveloped stuff will just eat away any benefits from Vim motions. I can see for certain command line based workflows it has some appeal, but for project IDE wotkflows it's just not there yet. Stuff is either missing or implemented worse than VSCode or CLion. YMMV.
What doesn't make sense is that he says in the video the problem with distro is that they are configured to somebody else's taste, isn't that what vscode is as well? lmao
That would be compaeable to just using vin out of the box. The problem with “the vim of someone else” is that is not something you built, AND is not standard (would lack documentation, etc)
What I usually do, is that if a plugin breaks something, then I throw a tag in there. Once I am ready to redo my setup I check to see if there is a need to move tags up to the new version.
I disagree, it's easier to start from the default and just add the few things you need instead of having to remove a bunch of stuff. Like I feel like if you are going to strip a districbution down anyway, why not just start from scratch?
@@officiallyaninjaOh, I see; I came to it from the coding perspective. I definitely keep a minimal version for simple text editing. But it's not going to cut it for me as opposed to a fully fledged IDE.
@@officiallyaninjaThe difference lies in what you know, basically. If you start from a bundle/distro that contains a lot of the stuff that's useful for you, you only need to look at that specific list, figure out what you don't need, and yeet it. If you start from blank... to build something effectively you need to already know what's out there, what exactly you need or not, what alternatives exist and their (dis)advantages etc. Also, not removing something because you didn't know you don't need it generally has minimal impact. Not knowing there's something you could add that would help because there's too much out there? That's more a problem.
i never used to use vim on windows and used vs code but after switching to linux i stop using vs code now it difficult for me to even use vs code occasionally , vim is such a great tool for make notes to writing code .
god this is so true. Back in my windows days (literally like 2 years ago, but it feels like for ever. I don't think I would know how to use Windows anymore, if you put me in front of a windows pc) I was absolutely against VS Code, but that was just because it was Microsoft, and I didn't really understand the concept op debugging (back when life was easy). Since Linux that has completely and utterly changed. I am addicted to my terminal, the speed and efficiency; everything. Because of that it causes me physical pain to leave it, so why bother with slow and over-complicated VSCode?
I do agree, if you want VS Code, use VS Code. However, it is worth noting, that my customized setup, ends up being fairly close to VS Code. The important part though is that what I have now I prefer over VS Code, it feels better, it's faster, it's closer to the terminal that I'm already in, I don't have to jump through JSON hoops. If I want to add remote plugin built in rust, I just do it. If I want a minimal script to run on save, I just add it. If I want to run external scripts on save, I just do it. It's all so simple, and yeah it takes a bit of work to get neovim where mine is, and yeah, occasionally my screen looks like a text based vscode, but I'm also 2 buttons from zen mode, and 1 to 2 buttons from whatever harpooned files I have, and one button from toggling auto format, a slightly different one for doing it on a single buffer. All of this with
I've been having the same experience as his. Neovim is still not stable enough for me, I guess. Neovim is still BETA. They are continuously introducing breaking changes. So maybe I will for Neovim to be finally officially release, and still only if they introduce some kind of non breaking changes approach, mainly to the LSP, and other core APIs. I wonder how long will that take though. I've tried to keep maintain my own neovim configuration for years, and in the end I have just got annoyed by the amount of changes. But I can see why some people like to keep doing it, not me.
@@ThePrimeTimeagenYou should check null-ls archived related issue. They have breaking changes every version or so. Now they may have reduced but the above commenter is right.
@@codingdesk3637 I'm a student and I don't have a job yet, so I can take that risk, but it doesn't matter, having a job wouldn't change that, my configuration doesn't break.
that selecting text thing prime does when he's reading articles where he selects an entire sentence except for the first and last letter xd i understand now :p
For me JetBrains + some vim motions is gold standard. If you don't see the thing on the screen, I use structural navigation, navigation to other file is easy and as fast as in Vim, and it actually works. I tried to setup Vim for C#, but damm, it's an uphill battle, not worth it at all. So Rider it is :)
Good to hear your thoughts on vim and Java, I'm stuck on the Java train for work. I was going to give neovim a try with it but I'd have to write a plugin to support Ivy dependency management first. Thinking I will just stick with Eclipse and the Vim plugin for now.
@@dan-frank I have tried it sadly the Ivy dependency management isn't as nice for the legacy projects I maintain. Maybe I should give it another look It's been a few years
As some who comes from many years of software enginering in on Windows using Visual Studio and VS Code, write a lot of C# but also in many other languages, widening my world to other operating systems and other tools in recent years was an amazing thing to do. I became a power user of Arch Linux last years, and this year it where both the Rust programming language and Vim which I learned and dived really deep into. After following an online training in Vim motions and commands the older and slower way of text editing from before did not feel right anymore, and so I installed the plugins in both VS and VS Code, also at work. I would say. AI driven code completion is 1 powerful tool you can use, the other one is this quicker way of text navigation and editing. That's how I think.
I would say that if you're switching to nvim from vs code, making it sort of look like vs code could help you be productive as you slowly remove the vs code features. I find I don't use the vs code vim motions extension despite that it's installed. Whereas as soon as I switch to vim I start using the vim motions
Huh, interesting. When I installed the vim motions plugin in CLion, I started picking them up pretty quick because there was no other way to navigate with it running.
The only thing that annoys me about daily driving NeoVim is not being able to just hit a button to run my project. I can have a build script or something, but it's annoying to run in a command line every time... having a run button is something I really miss. I got out of the habit of using a debugger while I was playing with DLL injection and couldn't figure out how to debug my remote code 😂
VSCode slaps, setting up for a new language takes a few clicks. Fewer if you use devcontainers. I don’t doubt there’s a higher speed ceiling on vim I just don’t think I’d ever get there.
I did vim for years but never customized a thing. Getting into neovim, NVChad was awesome. It gives you great defaults and then gets out of the way and lets you customize.
I'm a neo vim user with the PRIME setup from prime video. It's pretty cool and I use it every day. But I don't like messing around with vim too much. I just want a simple IDE for work, not a lot of customization. I still have vs code on my computer for copying and managing files, because it's way easier.
You touched on the reason I left emacs. Too many keybindings designed by someone else and a pressure to “give it a try” before naively creating my own bindings
This is kinda similar to what I do. I just use Neovim for text edits and Emacs for full IDE features (customised with LSP, EVIL, and intended to be customised similar to how Prime uses Vim).
11:00 sigh my dumass was trying to setup neovim up for a super large and oldish (Java 11) project. This caused like hours of grief for my neovim onboarding since Mason didn't have an LSP that supported that version and I got into a rabbithole of finding and learning how to set up LSPs (still trying to figure it out a few days later) I could really appreciate now how intellij just works out of the box. The setup process of vim has eaten away at my productivity is worrying but I still have some copium that this will make me a better/faster dev. I knew the learning curve would've been steep but dam this was eye opening to what a noob I am
4:33, in Codeblocks, I right click on the Render word, and 'Find occurrences of Render'. It finds it throughout the project files. Even so, it's not that fast, it takes around 1-2s. And to pass throughout them, I've to click on each occurrence, which is not as great as just passing through them.
@@ardnys35It seems to stay in an optimal point between VSCode/InteliJ and Vim-likes. It's middle-weight, it's not slow on Windows, has several good options, the more I discover the more I like it. And, the main reason: I've been fast enough developing with it. So I kept it.
Honestly I prefer regular vim to even neovim at this point. Also not really using autocomplete anymore except the regular CTRL+N completion (sometimes its even better honestly because it just continues text - also can continue whole lines actually!). I guess if I would use neovim, I would not really install plugins a lot. Pretty much like minimalism as-is - but I totally use it for development. I also think quick navigation to files where classes are is the better way to look for what to call than simple completion because it gives me more information so likely that is why I prefer that. I also prefer to be as familiar with the codebase (or learn to be very fast familiarizing) that completions would not really help that much and there is nothing faster than you already knowing what you want to write and you just write it out. For that CTRL+N is all I need because it just makes it faster for me to write it out - its not there for me to look what is possible but to write out what I want faster. Syntax highlight and netrw I do use though. Also use dwm with other terminals for various things and ranger for various tasks. I wish there would be debugger that runs in the terminal though - does anyone know one for js/ts??? I am very happy with raw gdb so I wish I have similar instead of using the browsers.......
man i'm not sure if its bait comment or not but neovim by default does not come with any lsp autocompletion or linting turned on by default it comes with exactly the same autocompletion (ctrl+n) that vim does, no difference it does come by default with the ABILITY to support lsps (aka lsp client) but you have to configure it for it to do anything you might've installed some sort of neovim distro if you had those things by default but neovim really only adds lsp-client, the lua engine (but it still supports vimrc), easy to setup tree-sitter (which i honestly can't go back after using it) and the obvious one which is a much more alive plugin eco system
@@Shun8734 It is not any bait comment I just not need the features of neovim that makes most people use neovim instead of vim. > neovim by default does not come with any lsp autocompletion or linting turned on > by default it comes with exactly the same autocompletion (ctrl+n) that vim does, no difference And no one said it comes with those. But if there is no difference and that is the only thing I basically tend to use, there is no gain for me in neovim isn't it? > it does come by default with the ABILITY to support lsps (aka lsp client) but you have to configure it for it to do anything I actually think LSP was a bad idea overall. I know... I know... it solves your problems... My point is that it solves problems in a very overbloated way... So not caring for LSP support... > you might've installed some sort of neovim distro if you had those things by default Read my comment again - also cleared this up above for you. > but neovim really only adds lsp-client, the lua engine (but it still supports vimrc), easy to setup tree-sitter (which i honestly can't go back after using it) and the obvious one which is a much more alive plugin eco system - lsp client: I am not liking LSP at all and hope it will be one day exchanged to a better system with less json and less bloat so not care - lua: Not really a big fan of lua. I am not against it objectively, just subjectively not really big fan at all. But unlike with LSP which I think objectively is bad, for lua I just subjectively have no interest so its just not a selling point. I can understand it can be selling point for other people - just personally not affected... - tree-sitter: Again... not really interested, also not totally sure about it if I am just subjectively not interested or if bloated because not decided yet, but really not giving me much. - plugin ecosystem: As I said I pretty much not use plugins. Again I quote what I wrote originally: "I guess if I would use neovim, I would not really install plugins a lot. Pretty much like minimalism as-is" - which hints to you (I thought its a clear message) that yes, I could use neovim as a more bloated vim replacement with features and plugins that I do not use.... but what is the point of doing that? I think the reason to use neovim it to DO USE those features! For example you say you DO use those features: Good. I see why you like neovim. But for me regular vim with a normal regular setup is less bloated and do everything I need whatsoever so what is the point? The few things I want to change I am fine to vimscript down because they are very few and custom anyways so not really losing out on features that nvim makes possible. Do you understand my point?
@@u9vata its okay man i'm not trying to convince you, just wanted to make sure people don't read the comment and assume neovim comes with all this stuff
17:30 Even on a MacBook 2023 GUI is slower than text, then again I do prefer and old BIOS-like interface with no GUI what so ever for tmux/vim, only exception is when having to check web browser, hence I do prefer 2 monitors.
My biggest gripe with Vim Motions is.... myself. I have a hard time getting off the habit of navigating the code with arrow keys instead of hjkl. Habits built over two decades are hard to unlearn, and I also just generally like the tetris t-block shape for my movement, like arrows or wasd. Other vim motion stuff like selecting words, removing lines, etc, are easier to learn because they're generally new. But simple navigation of the caret, man oh man
@@gbroton I don't really plan to vim-ify anything else that uses arrow keys for navigation, but I probably should tbh. Edit: Should as in change arrow keys on nvim
Hate to say it, but this video 100% convinced me to just approach Neovim as a nifty-nerd tool I'll mess around with in my free time but continue to use VSCodium for all of my serious projects. For terminal use I'll probably just stick to Vim and Micro and just learn dbg the hard way, combined with tmux. This is the way Unix systems were more or less intended to be used anyway, simple systems that do one thing well... easy to use, easy to maintain, easy to reinvent.
LSPs in my experience sound great until you actually try using them... I have never had a state where one was just working for me, and that's the reason I stick with IDEs or Pseudo-IDEs like VSC personally.
I started to say SQL the same way you do as I find that it sound better and is easier to say, since then my friend tells me everyday " It's S-Q-L not SQEEL!"
I think people are trying to create a VSCode workflow in Neovim just because they have gotten used to using a similar flow like they had in Sublime, Atom, and VSCode. This is just an entry point, just to do something to feel comfortable. Only after that, you can realize that you don't need certain things and will find a much cooler approach to figuring out and making your workflow better or just different. And of course you can't create your custom exp, just because you had exp with typical code editors.
Yup, the whole problem is trying to use (neo)vim as you would use gui editor, without even changing your workflow. It's not unlike going into vim and rejecting motions and modes except insert mode, using it like regular editor and then saying "it sucks". Well, yeah, if you use it like that it does.
All the plugins are done to VSCode's defacto standard of LSP, and everyone gets to follow VSCode's idiosyncrasies if they want it to work in their editor too
Debugging work fine in nvim, just need to setup DAP and start the app in debug mode. The reason why I prefer nvim to vs code is because I can do everything on the keyboard and I have my editor in a drop down terminal so I navigate inside vim, between tmux panes and windows all in the same place with the keyboard. You cannot do that easily with vscode and it is not that seamlessly integrated. Java works in nvim with the lsp, the major problem with java is that IntelliJ ha so much more built specifically for JVM on top of LSP..
I have rebuilt my PDE based on kickstart. It performs much better now and removed unused plugins that I had installed in the past. Simplified use of plugins. #worksforme
Can't edit code without vim motions since ehm, the year 2000. Every IDE I use has to have them. Including markdown editors. Got Java and Neovim to work together eventually, not using it for daily work (forced to use windows being one reason). But for hobby work I did not dislike it. Main complaint is that the LSP (jdtls) is like a limb cut off from eclipse and is quite a seven headed picky dragon. If there is another LSP for Java I'd be glad to investigate.But yes, IntelliJ is quite unbeaten in Java development land.
Iv just started using Vim on vscode, just learning the keyboard controls. Im slower, and it's a paradigm shift, but even after a few hours, I was starting to feel how it actually is easier coding.
vim felt completely impenetrable to me, despite using a distro for a bit, until I got kickstart and watched TJ's video on kickstart. I would say I'm still definitely a novice at vim but I actually feel like I made forward progress and understood something after working with kickstart for just a couple of hours.
I also moved away from nvim purely because of the plugin breaking changes. I dont have time to fix something I expect to be stable. I will however give the vscode neovim plugin a go! I tried the vim plugin and my god it was so slow you can see the delay on keystrokes also its buggy and breaks some of the existing functionality of vscode
I've been using neovim for go development for a year now and before for Python development. Switched from vscode and never looked back. I don't get his point that his neovim constantly breaks. I don't remember when neovim broke last time for me or crashed. It performs super smoothly on a medium sized codebase, the lsp provides all the features I need and I even have a debugging experience. Sure, its worse than vscode's or Jetbrains IDE as it is "just" terminal-based, but it gets the job done, especially as I am using it mostly to run unit tests and set breakpoints in the tested code. Plus I don't need a lot of plugins to make it vscode like as I also use telescope with alternative file thus making tabs obsolete.
I don't get why some people feel they SHOULD be using something. Use whatever you want! If someone is forcing you to use a text editor call the authorities. With that said I love nvim. I used vscode the first couple years of my career and always found it slow to startup, to move through files, clicking on things etc. Just don't use a pre configured template/starter/configuration/whatever and do it from scratch, it isn't that hard and if you use the most fundamental and necessary plugins I don't think it's that fragile.
its not that one thing is the goal, its that exposure should be the goal. you _should_ use neovim for a month and understand its benefit and how it changes the way you think
@@ThePrimeTimeagen hmm... then maybe pre built configuration is a good place to start to get familiarized with nvim yeah, I guess the hard part about it is to get over the hump of learning the motions. I was going to say that I'm not sure if it changes the way you think because it sounds like too big of a thing for a change of text editor, but now that I look back at it, it did teach me to just read the docs of anything to achieve what you want way more than reading through a package has... you need to learn what is an lsp and how to install them, where they're at, managing them, connecting it to formatters and to an autocompletion plugin maybe etc. And then you nvim from terminal and it gives you no warnings or errors gawddamn I love neovim
I got off lunarvim and moving to lazy vim. There's only so much time I can spend on my editor. I really do plan to dig in, but it wont be enough time spent in vim I keep switching because X isn't configured.
Imo it's easier to start from scratch then a distro. I tried lunarvim, lazy im and Kickstart and I only managed to use nvim after doing it from scratch following a blog tutorial. And it was so much easier you would not believe it
I'm fresh with Nvim, but I think I disagree with the point that debuggers dont work in Nvim. I have limited experience with it so far, but I use a debugger sometimes when writing C and I haven't faced any issues with it yet
Thats... a really reasonable take... goddamnit where is the mudslinging? The pitchforks? Where is the fire that consumes everything for absolutely no reason?
To be personally honing your tools is a weird concept to me. Why would I want to spend a lot of time changing my hammer instead of doing actual carpentry? It only happens in IT. I'm learning Vim motions because of the ergonomics of it, but the idea of changing the tool to my liking instead of just using a made one is boggus to me. I doubt a guy with a wife and family is able to sustain this.
If you are in the Vim progression long enough you come to a point where you realize that adding more and more plugins doesn't make you faster. It's often just some cool features that sound useful on paper, but that don't have that much use in the real world or you already have a simple but maybe not 100% optimal number of key strokes way to do the thing with the basic tools. The same is 100% true for vscode, the number of features some plugins ship is just insane. Just learn to get good with the basics and you get 95% of the way there, instead of finding plugins to fill the gaps for you.
I find a debugger is really nice to have for python, its a pain in the ass to look at unannotated code and try to figure out what types things are supposed to be runtime. I use nvim-dap-ui to debug in nvim
Same but, i think dap-ui is nowhere near at what i have in pycharm, so most of the time if i want debugger i just avoid dap-ui and use pycharm. E.g if you want to debug Django, with dap-ui you can only do with tests. Otherwise you have to attach debugger to Django process and it is just pain in ass.
I prefer vscode over vim because i'm not interested to build my own personal ide and spend time configuring a text editor. I just want something that works and if needed i'll change a few defaults. Any of the neovim distributions have not been straight forward and they have had custom keybinding for so many things. I don't want any custom keybindings to learn, that won't be applicable to know on a default install. I wan't a text editor that has good defaults.
I use vim when in the terminal and a vim extension in vscode. I also edit code quite much in vim where I have a few plugins. But I'm totally not interested to spend hours on configurations and testing various half-buggy plugins or distributions. Also I don't understand why using code (lua) as your configuration is a good idea. I understand that using a programming language is code if you want to create an extension that uses an api, but if i just want to add settings/keybindings/list plugins to load, why does it nee to be in lua?
working without a debugger sounds very foreign/uncomfortable to me. I tried setting up DAP in neovim today and it was enough of a pain that I'm sticking with intellij
i kinda dislike vim default keybindings, but i feel like if i change any bindings, then i wouldnt be able to neither do stuff at other places whenever the vim is required, nor be ok at using non-vim editors because i would get annoyed at missing all the vim goodness. so ill just stick to default intellij keybindings which are easy to get on both vscode and ij and just zoop with its double shift quick goto and actions and alt+j multiselect similar
@@gritcrit4385 nope! Telescope can search through files, buffers, strings (like a grep), help documentation, keymaps, quick fix lists… just about anything. It’s a fairly generic use tool!
YES PRIME, we are waiting for neovim setup from scratch part 2
Please 🙏
Wasn’t ChrisAtMachine the guy who had a Neovim from scratch series? Unfortunately he scrapped it a bit, and now just distributes a fully baked LunarVim.
He uses mostly defaults, lol
@@Slashx92 g
+1
Tom one day said: “Requires experience to want a custom experience”
this is a really good phrase
Tom is a genius.
Tom is a genius, indeed
“You don’t look 40 but your editor choice sure confirms it“ gottim!
still hurts
The trick is to stop reading after the but. Positive statement + but = danger
@@ThePrimeTimeagen but that's the truth. You are 40 if you are 40. I knew a guy in his 20s who used vim for almost everything so editor doesn't confirm it!
@@VaibhavKaushal-qt9pr
He was 40 at heart.
12:44 would be great if you could show how you structure your code to achieve this. I know a bunch of people say "well separate your ins and outs from your logic" and stuff like that but having a real tangible example would be great
It took me like a week to properly configure nvim with lazy, lsp, treesitter, telescope and other desired plugins. The configuration I'll probably be happy about for the next couple of years. Knowing what every line does and being able to provide any possible customization I might want, where everything is set up exactly for your needs. This feeling is quite impossible to get with any other editor.
its because it is
Prime, nixos is this for operating systems.
What do you mean by "Knowing what every line does"?
when you make a vim config, it's all one configuration and so you can know what every line of your config does. kind of like settings.json + extensions.json + keybindings.json in vscode, but at the end of the day you still don't know how vscode works it's all.. magic @@MrAbrazildo
In config I'm guessing@@MrAbrazildo
Being very old, I use vi.
Well, that is pointed to neovim now. I'm on the keyboard;
Fingers do that.
ee gets me file search
hm gets me harpoon
It also compiles fine on a Raspberry Pi arm6 - 0.9.1 (not that I code on that, I cross compile, I compile it to make sure system is good)
lets go!
True, Vim Motions are an UX ecosystem in their self. Not only Vim uses them, a lot of Unix tooling does
Actually they are Vi and Ex motions and commands, Vim was later developed to be an improved Vi.
And if I am not wrong, Vi was even a kind of an extension to Ex, which was also based on some kind of older tool if I am right with that too.
Maybe some older Unix gurus are reading this and can add more information here.
Wikipedia says something to the effect of "ex"
I don't think ex was a visual editor with motion commands, but some of the line edit commands, like in the s/ and "sed" type syntax, resemble the vi commands. Vi is the visual version of ex
I use vim all the time, but I never develop with it.
What do you use it for? Writing novels?
@@vikingthedudeI have it started in the background so I can look smart when I need to share my screen with colleague
@@Z3rgatulGIGACHAD
@@vikingthedude Anything and everything related to editing text outside of development. I even have my file binding for txt files set to open vim in a CLI, I just don't write code using vim.
Kickstart is magic, I started with it. It is the bare minimum to understand how vim works without a ton of overwhelming features. Once I got the basics I replaced it with my custom version and boom
Exactly what I did as well a few days ago. Works like a charm right out of the box
I set up NeoVim using Kickstart today after re-installing Linux. After I added some of prime's suggested keybinds and harpoon, it's pretty much perfect. I put my edits on a fork and now I can get up and running in like 15 seconds 😁
fr the main issue i had with neovim "distro"s is that over a certain level of customization you need to look into its implementation specific, outside of how im supposed to configure it. as those distros have quite complicated implementation, its hard to do so, while kickstart.nvim exactly solves that as its (almost) a single lua file with about 300-ish lines of code excluding comments
You mean NEOvim.
It's like Arch Users, love women but never have a girlfriend!!
There's a word for Arch/NixOS/Emacs/[Neo]Vim users now: *"incels".*
I had sone downtime last w/e so gave neovim a shot. Took a long afternoon to set it up. C/C++ dev with fairly large projects. Used VSCode, currently using CLion. Conclusion, I kinda get the keyboard speed thing. The tooling though isn't a patch on CLion (or VSCode) for large scale C/C++ dev, profiling and debugging. Customising and config is a PITA especially when you just want to get wotk done. Pain points on underdeveloped stuff will just eat away any benefits from Vim motions. I can see for certain command line based workflows it has some appeal, but for project IDE wotkflows it's just not there yet. Stuff is either missing or implemented worse than VSCode or CLion. YMMV.
I'm always using a debugger. I like to see the flow of any complicated (relative) fn of class.
What doesn't make sense is that he says in the video the problem with distro is that they are configured to somebody else's taste, isn't that what vscode is as well? lmao
That would be compaeable to just using vin out of the box. The problem with “the vim of someone else” is that is not something you built, AND is not standard (would lack documentation, etc)
That kid spoke the truth. I learned vim I rarely use it nowadays. I value my time.
What I usually do, is that if a plugin breaks something, then I throw a tag in there. Once I am ready to redo my setup I check to see if there is a need to move tags up to the new version.
Removing "bloat" is way easier than spending a lot of time perfecting your build, so distributions are THE way to go for people that have lives.
I disagree, it's easier to start from the default and just add the few things you need instead of having to remove a bunch of stuff.
Like I feel like if you are going to strip a districbution down anyway, why not just start from scratch?
@@officiallyaninjaOh, I see; I came to it from the coding perspective.
I definitely keep a minimal version for simple text editing. But it's not going to cut it for me as opposed to a fully fledged IDE.
@@officiallyaninjaThe difference lies in what you know, basically.
If you start from a bundle/distro that contains a lot of the stuff that's useful for you, you only need to look at that specific list, figure out what you don't need, and yeet it. If you start from blank... to build something effectively you need to already know what's out there, what exactly you need or not, what alternatives exist and their (dis)advantages etc.
Also, not removing something because you didn't know you don't need it generally has minimal impact. Not knowing there's something you could add that would help because there's too much out there? That's more a problem.
i never used to use vim on windows and used vs code but after switching to linux i stop using vs code now it difficult for me to even use vs code occasionally , vim is such a great tool for make notes to writing code .
Gotem
god this is so true. Back in my windows days (literally like 2 years ago, but it feels like for ever. I don't think I would know how to use Windows anymore, if you put me in front of a windows pc) I was absolutely against VS Code, but that was just because it was Microsoft, and I didn't really understand the concept op debugging (back when life was easy). Since Linux that has completely and utterly changed. I am addicted to my terminal, the speed and efficiency; everything. Because of that it causes me physical pain to leave it, so why bother with slow and over-complicated VSCode?
@@daxtheducknotaffiliated Sounds like you're addicted
I do agree, if you want VS Code, use VS Code.
However, it is worth noting, that my customized setup, ends up being fairly close to VS Code.
The important part though is that what I have now I prefer over VS Code, it feels better, it's faster, it's closer to the terminal that I'm already in, I don't have to jump through JSON hoops. If I want to add remote plugin built in rust, I just do it. If I want a minimal script to run on save, I just add it. If I want to run external scripts on save, I just do it.
It's all so simple, and yeah it takes a bit of work to get neovim where mine is, and yeah, occasionally my screen looks like a text based vscode, but I'm also 2 buttons from zen mode, and 1 to 2 buttons from whatever harpooned files I have, and one button from toggling auto format, a slightly different one for doing it on a single buffer.
All of this with
I've been having the same experience as his. Neovim is still not stable enough for me, I guess. Neovim is still BETA. They are continuously introducing breaking changes. So maybe I will for Neovim to be finally officially release, and still only if they introduce some kind of non breaking changes approach, mainly to the LSP, and other core APIs. I wonder how long will that take though.
I've tried to keep maintain my own neovim configuration for years, and in the end I have just got annoyed by the amount of changes. But I can see why some people like to keep doing it, not me.
real talk, give me a breaking change?
@@ThePrimeTimeagenYou should check null-ls archived related issue. They have breaking changes every version or so. Now they may have reduced but the above commenter is right.
then use regular vim.
I update my plugins almost daily and it never breaks.
How do you get any work done? Madman.
@@codingdesk3637 I'm a student and I don't have a job yet, so I can take that risk, but it doesn't matter, having a job wouldn't change that, my configuration doesn't break.
The engagement remark is so on point. I know a MtG streamer who mispronounces chat members' names on purpose as a tool of the trade. Works perfectly!
that selecting text thing prime does when he's reading articles where he selects an entire sentence except for the first and last letter xd
i understand now :p
5:00 use the right tool for the job? Nah, use the right job for the language 🦀
😂😂😂
For me JetBrains + some vim motions is gold standard. If you don't see the thing on the screen, I use structural navigation, navigation to other file is easy and as fast as in Vim, and it actually works. I tried to setup Vim for C#, but damm, it's an uphill battle, not worth it at all. So Rider it is :)
th-cam.com/video/KpudmVmMWx4/w-d-xo.html
Good to hear your thoughts on vim and Java, I'm stuck on the Java train for work. I was going to give neovim a try with it but I'd have to write a plugin to support Ivy dependency management first. Thinking I will just stick with Eclipse and the Vim plugin for now.
I'd recommend InteliJ for Java, I found it was a significantly nicer experience over Eclipse. Also has a Vim plugin 👍
@@dan-frank I have tried it sadly the Ivy dependency management isn't as nice for the legacy projects I maintain. Maybe I should give it another look It's been a few years
As some who comes from many years of software enginering in on Windows using Visual Studio and VS Code, write a lot of C# but also in many other languages, widening my world to other operating systems and other tools in recent years was an amazing thing to do.
I became a power user of Arch Linux last years, and this year it where both the Rust programming language and Vim which I learned and dived really deep into.
After following an online training in Vim motions and commands the older and slower way of text editing from before did not feel right anymore, and so I installed the plugins in both VS and VS Code, also at work.
I would say. AI driven code completion is 1 powerful tool you can use, the other one is this quicker way of text navigation and editing. That's how I think.
I'm glad you used the phrase "do the thing" because with all this faff, i forgot to do my work lol
I would say that if you're switching to nvim from vs code, making it sort of look like vs code could help you be productive as you slowly remove the vs code features. I find I don't use the vs code vim motions extension despite that it's installed. Whereas as soon as I switch to vim I start using the vim motions
Huh, interesting. When I installed the vim motions plugin in CLion, I started picking them up pretty quick because there was no other way to navigate with it running.
@@torphedo6286 I do a lot of copy/pasting. I just left it in edit mode the whole time and never use any vim motions.
Great point about debugging. If you can't reproduce it with a test, you don't know what you're trying to fix.
The only thing that annoys me about daily driving NeoVim is not being able to just hit a button to run my project. I can have a build script or something, but it's annoying to run in a command line every time... having a run button is something I really miss. I got out of the habit of using a debugger while I was playing with DLL injection and couldn't figure out how to debug my remote code 😂
Newb here, couldn’t you make a keybinding to run that build command?
VSCode slaps, setting up for a new language takes a few clicks. Fewer if you use devcontainers.
I don’t doubt there’s a higher speed ceiling on vim I just don’t think I’d ever get there.
Ironically, what Prime does with his Vim is exactly what I did with my VSCode. VSCode is INCREDIBLY customizable
I did vim for years but never customized a thing. Getting into neovim, NVChad was awesome. It gives you great defaults and then gets out of the way and lets you customize.
I'm a neo vim user with the PRIME setup from prime video. It's pretty cool and I use it every day. But I don't like messing around with vim too much. I just want a simple IDE for work, not a lot of customization. I still have vs code on my computer for copying and managing files, because it's way easier.
You touched on the reason I left emacs. Too many keybindings designed by someone else and a pressure to “give it a try” before naively creating my own bindings
This is kinda similar to what I do. I just use Neovim for text edits and Emacs for full IDE features (customised with LSP, EVIL, and intended to be customised similar to how Prime uses Vim).
11:00 sigh my dumass was trying to setup neovim up for a super large and oldish (Java 11) project.
This caused like hours of grief for my neovim onboarding since Mason didn't have an LSP that supported that version and I got into a rabbithole of finding and learning how to set up LSPs (still trying to figure it out a few days later)
I could really appreciate now how intellij just works out of the box.
The setup process of vim has eaten away at my productivity is worrying but I still have some copium that this will make me a better/faster dev. I knew the learning curve would've been steep but dam this was eye opening to what a noob I am
Absolute rollercoaster of emotions at the start there...
4:33, in Codeblocks, I right click on the Render word, and 'Find occurrences of Render'. It finds it throughout the project files. Even so, it's not that fast, it takes around 1-2s. And to pass throughout them, I've to click on each occurrence, which is not as great as just passing through them.
code::blocks? why?
@@ardnys35It seems to stay in an optimal point between VSCode/InteliJ and Vim-likes. It's middle-weight, it's not slow on Windows, has several good options, the more I discover the more I like it. And, the main reason: I've been fast enough developing with it. So I kept it.
We don't use the mouse here
@@halamadrid5238Ok. I'm just saying that mouse is not bad: it's comfortable, being just a little slower.
I've actually been on a vim motions hiatus of sorts. It's so good to be back though, it's hard to truly appreciate something until you lose it.
Honestly I prefer regular vim to even neovim at this point. Also not really using autocomplete anymore except the regular CTRL+N completion (sometimes its even better honestly because it just continues text - also can continue whole lines actually!).
I guess if I would use neovim, I would not really install plugins a lot. Pretty much like minimalism as-is - but I totally use it for development. I also think quick navigation to files where classes are is the better way to look for what to call than simple completion because it gives me more information so likely that is why I prefer that. I also prefer to be as familiar with the codebase (or learn to be very fast familiarizing) that completions would not really help that much and there is nothing faster than you already knowing what you want to write and you just write it out. For that CTRL+N is all I need because it just makes it faster for me to write it out - its not there for me to look what is possible but to write out what I want faster.
Syntax highlight and netrw I do use though. Also use dwm with other terminals for various things and ranger for various tasks. I wish there would be debugger that runs in the terminal though - does anyone know one for js/ts??? I am very happy with raw gdb so I wish I have similar instead of using the browsers.......
man i'm not sure if its bait comment or not but
neovim by default does not come with any lsp autocompletion or linting turned on
by default it comes with exactly the same autocompletion (ctrl+n) that vim does, no difference
it does come by default with the ABILITY to support lsps (aka lsp client) but you have to configure it for it to do anything
you might've installed some sort of neovim distro if you had those things by default
but neovim really only adds lsp-client, the lua engine (but it still supports vimrc), easy to setup tree-sitter (which i honestly can't go back after using it) and the obvious one which is a much more alive plugin eco system
@@Shun8734 It is not any bait comment I just not need the features of neovim that makes most people use neovim instead of vim.
> neovim by default does not come with any lsp autocompletion or linting turned on
> by default it comes with exactly the same autocompletion (ctrl+n) that vim does, no difference
And no one said it comes with those. But if there is no difference and that is the only thing I basically tend to use, there is no gain for me in neovim isn't it?
> it does come by default with the ABILITY to support lsps (aka lsp client) but you have to configure it for it to do anything
I actually think LSP was a bad idea overall. I know... I know... it solves your problems... My point is that it solves problems in a very overbloated way... So not caring for LSP support...
> you might've installed some sort of neovim distro if you had those things by default
Read my comment again - also cleared this up above for you.
> but neovim really only adds lsp-client, the lua engine (but it still supports vimrc), easy to setup tree-sitter (which i honestly can't go back after using it) and the obvious one which is a much more alive plugin eco system
- lsp client: I am not liking LSP at all and hope it will be one day exchanged to a better system with less json and less bloat so not care
- lua: Not really a big fan of lua. I am not against it objectively, just subjectively not really big fan at all. But unlike with LSP which I think objectively is bad, for lua I just subjectively have no interest so its just not a selling point. I can understand it can be selling point for other people - just personally not affected...
- tree-sitter: Again... not really interested, also not totally sure about it if I am just subjectively not interested or if bloated because not decided yet, but really not giving me much.
- plugin ecosystem: As I said I pretty much not use plugins.
Again I quote what I wrote originally: "I guess if I would use neovim, I would not really install plugins a lot. Pretty much like minimalism as-is" - which hints to you (I thought its a clear message) that yes, I could use neovim as a more bloated vim replacement with features and plugins that I do not use.... but what is the point of doing that? I think the reason to use neovim it to DO USE those features! For example you say you DO use those features: Good. I see why you like neovim. But for me regular vim with a normal regular setup is less bloated and do everything I need whatsoever so what is the point? The few things I want to change I am fine to vimscript down because they are very few and custom anyways so not really losing out on features that nvim makes possible. Do you understand my point?
@@u9vata its okay man i'm not trying to convince you, just wanted to make sure people don't read the comment and assume neovim comes with all this stuff
17:30 Even on a MacBook 2023 GUI is slower than text, then again I do prefer and old BIOS-like interface with no GUI what so ever for tmux/vim, only exception is when having to check web browser, hence I do prefer 2 monitors.
not everyone is worthy for the power of neovim
My biggest gripe with Vim Motions is.... myself. I have a hard time getting off the habit of navigating the code with arrow keys instead of hjkl. Habits built over two decades are hard to unlearn, and I also just generally like the tetris t-block shape for my movement, like arrows or wasd.
Other vim motion stuff like selecting words, removing lines, etc, are easier to learn because they're generally new. But simple navigation of the caret, man oh man
Disable arrows in your editor, two days and you will pick up hjkl :)
@@gbroton I don't really plan to vim-ify anything else that uses arrow keys for navigation, but I probably should tbh.
Edit: Should as in change arrow keys on nvim
Just continue using arrows
what about a keyboard without the arrow keys?
You shouldn't be using hjkl either, learn to use wbe ft and the search
My parent never bought me a new laptop to use that chunky VSCode that's why I learn VIM
Hate to say it, but this video 100% convinced me to just approach Neovim as a nifty-nerd tool I'll mess around with in my free time but continue to use VSCodium for all of my serious projects. For terminal use I'll probably just stick to Vim and Micro and just learn dbg the hard way, combined with tmux. This is the way Unix systems were more or less intended to be used anyway, simple systems that do one thing well... easy to use, easy to maintain, easy to reinvent.
LSPs in my experience sound great until you actually try using them... I have never had a state where one was just working for me, and that's the reason I stick with IDEs or Pseudo-IDEs like VSC personally.
I started to say SQL the same way you do as I find that it sound better and is easier to say, since then my friend tells me everyday " It's S-Q-L not SQEEL!"
I am watching this on SteamOS, and when he patted his head I was tapping the volume buttons. plop plop.
I think people are trying to create a VSCode workflow in Neovim just because they have gotten used to using a similar flow like they had in Sublime, Atom, and VSCode. This is just an entry point, just to do something to feel comfortable. Only after that, you can realize that you don't need certain things and will find a much cooler approach to figuring out and making your workflow better or just different. And of course you can't create your custom exp, just because you had exp with typical code editors.
Yup, the whole problem is trying to use (neo)vim as you would use gui editor, without even changing your workflow. It's not unlike going into vim and rejecting motions and modes except insert mode, using it like regular editor and then saying "it sucks". Well, yeah, if you use it like that it does.
All the plugins are done to VSCode's defacto standard of LSP, and everyone gets to follow VSCode's idiosyncrasies if they want it to work in their editor too
Debugging work fine in nvim, just need to setup DAP and start the app in debug mode. The reason why I prefer nvim to vs code is because I can do everything on the keyboard and I have my editor in a drop down terminal so I navigate inside vim, between tmux panes and windows all in the same place with the keyboard. You cannot do that easily with vscode and it is not that seamlessly integrated. Java works in nvim with the lsp, the major problem with java is that IntelliJ ha so much more built specifically for JVM on top of LSP..
I use a simple neovim setup for text editing, and other software for more specific tooling.
the feelings you want to feel are on the other side of the feelings you don't want to feel
I have rebuilt my PDE based on kickstart. It performs much better now and removed unused plugins that I had installed in the past. Simplified use of plugins. #worksforme
Can't edit code without vim motions since ehm, the year 2000. Every IDE I use has to have them. Including markdown editors.
Got Java and Neovim to work together eventually, not using it for daily work (forced to use windows being one reason). But for hobby work I did not dislike it. Main complaint is that the LSP (jdtls) is like a limb cut off from eclipse and is quite a seven headed picky dragon. If there is another LSP for Java I'd be glad to investigate.But yes, IntelliJ is quite unbeaten in Java development land.
Iv just started using Vim on vscode, just learning the keyboard controls. Im slower, and it's a paradigm shift, but even after a few hours, I was starting to feel how it actually is easier coding.
Me thinking what the hell is this guy sipping throughout the entire video. DOes it have beans in it!?!?!
agreed with non-landing, i never use it. just hydrate session from the project's directory and off to the races
vim felt completely impenetrable to me, despite using a distro for a bit, until I got kickstart and watched TJ's video on kickstart. I would say I'm still definitely a novice at vim but I actually feel like I made forward progress and understood something after working with kickstart for just a couple of hours.
I decided to learn Natural and Adabas because a company my friend works in needs developers. It's in eclipse...
22:37 internet was already like this way before chatgpt was even in the mind of the creators
I use emacs mostly but I also use vscodium and I've been trying out helix recently (basically a rust version of NeoVim).
Eric Murphy is great, actually I landed on your channel because of him!
It's chat gepetee
For the yt algo my boi!
He basically said vim is sublime text to him.
I also moved away from nvim purely because of the plugin breaking changes. I dont have time to fix something I expect to be stable. I will however give the vscode neovim plugin a go! I tried the vim plugin and my god it was so slow you can see the delay on keystrokes also its buggy and breaks some of the existing functionality of vscode
amazing video! I learn much and laugh more
I've been using neovim for go development for a year now and before for Python development. Switched from vscode and never looked back. I don't get his point that his neovim constantly breaks. I don't remember when neovim broke last time for me or crashed. It performs super smoothly on a medium sized codebase, the lsp provides all the features I need and I even have a debugging experience. Sure, its worse than vscode's or Jetbrains IDE as it is "just" terminal-based, but it gets the job done, especially as I am using it mostly to run unit tests and set breakpoints in the tested code. Plus I don't need a lot of plugins to make it vscode like as I also use telescope with alternative file thus making tabs obsolete.
I don't get why some people feel they SHOULD be using something. Use whatever you want! If someone is forcing you to use a text editor call the authorities.
With that said I love nvim. I used vscode the first couple years of my career and always found it slow to startup, to move through files, clicking on things etc. Just don't use a pre configured template/starter/configuration/whatever and do it from scratch, it isn't that hard and if you use the most fundamental and necessary plugins I don't think it's that fragile.
its not that one thing is the goal, its that exposure should be the goal.
you _should_ use neovim for a month and understand its benefit and how it changes the way you think
@@ThePrimeTimeagen hmm... then maybe pre built configuration is a good place to start to get familiarized with nvim yeah, I guess the hard part about it is to get over the hump of learning the motions.
I was going to say that I'm not sure if it changes the way you think because it sounds like too big of a thing for a change of text editor, but now that I look back at it, it did teach me to just read the docs of anything to achieve what you want way more than reading through a package has... you need to learn what is an lsp and how to install them, where they're at, managing them, connecting it to formatters and to an autocompletion plugin maybe etc.
And then you nvim from terminal and it gives you no warnings or errors gawddamn I love neovim
someone at work convinced me to use i3wm and now they are slowly getting me to use neovim
How did you set up jumping to reference lines in the main buffer when you go up and down in the float window?
SO when is that neovim setup from scratch part 2 coming?
I like both but I’m not leaving eMacs for my main projects
Ironically, I switched to Neovim from VS Code because VS Code kept breaking my setup with each update.
I got off lunarvim and moving to lazy vim. There's only so much time I can spend on my editor.
I really do plan to dig in, but it wont be enough time spent in vim I keep switching because X isn't configured.
Imo it's easier to start from scratch then a distro. I tried lunarvim, lazy im and Kickstart and I only managed to use nvim after doing it from scratch following a blog tutorial. And it was so much easier you would not believe it
@18:26 💀 "To be one with your tool!
I'm fresh with Nvim, but I think I disagree with the point that debuggers dont work in Nvim. I have limited experience with it so far, but I use a debugger sometimes when writing C and I haven't faced any issues with it yet
I'd say he was off by 2.0 or 29, not sure which one, 40 flat just doesn't seem right
I think is it ok to use nvchad astro etc to starting out once you get more comfortable then you can customized it to your own way
prime: "WHO USES NORD?!!?!"
r/unixporn: 👁👄👁
Thats... a really reasonable take... goddamnit where is the mudslinging? The pitchforks? Where is the fire that consumes everything for absolutely no reason?
It's very hard for me to use VS Code, after using nvim, even when I use the vim plugin, it just feels like I am doing something wrong.
To be personally honing your tools is a weird concept to me. Why would I want to spend a lot of time changing my hammer instead of doing actual carpentry? It only happens in IT. I'm learning Vim motions because of the ergonomics of it, but the idea of changing the tool to my liking instead of just using a made one is boggus to me. I doubt a guy with a wife and family is able to sustain this.
Prime how do you deal with the possibility of plugins being malicious and contain malware?
If you are in the Vim progression long enough you come to a point where you realize that adding more and more plugins doesn't make you faster. It's often just some cool features that sound useful on paper, but that don't have that much use in the real world or you already have a simple but maybe not 100% optimal number of key strokes way to do the thing with the basic tools. The same is 100% true for vscode, the number of features some plugins ship is just insane. Just learn to get good with the basics and you get 95% of the way there, instead of finding plugins to fill the gaps for you.
2:15 Looks like GO html templates ("html/template").
I find a debugger is really nice to have for python, its a pain in the ass to look at unannotated code and try to figure out what types things are supposed to be runtime. I use nvim-dap-ui to debug in nvim
Same but, i think dap-ui is nowhere near at what i have in pycharm, so most of the time if i want debugger i just avoid dap-ui and use pycharm.
E.g if you want to debug Django, with dap-ui you can only do with tests. Otherwise you have to attach debugger to Django process and it is just pain in ass.
If you're really lazy about customizing, something like lazyvim seems like a good compromise.
Anyone know what this search is that he's doing at 13:51 ? Looks like searching a list of projects outside of the current vim working directory
I prefer vscode over vim because i'm not interested to build my own personal ide and spend time configuring a text editor. I just want something that works and if needed i'll change a few defaults. Any of the neovim distributions have not been straight forward and they have had custom keybinding for so many things. I don't want any custom keybindings to learn, that won't be applicable to know on a default install. I wan't a text editor that has good defaults.
I use vim when in the terminal and a vim extension in vscode. I also edit code quite much in vim where I have a few plugins. But I'm totally not interested to spend hours on configurations and testing various half-buggy plugins or distributions. Also I don't understand why using code (lua) as your configuration is a good idea. I understand that using a programming language is code if you want to create an extension that uses an api, but if i just want to add settings/keybindings/list plugins to load, why does it nee to be in lua?
6:10 had me close to tears 😂
I wish my code knowledge and productivity could justify the use of NVim.
I use Vim to update my configs and add plugins.
Nord user here. 😞
It's one of the few themes that I can stand for prolonged periods of time because of its low contrast.
working without a debugger sounds very foreign/uncomfortable to me. I tried setting up DAP in neovim today and it was enough of a pain that I'm sticking with intellij
I had a good experience with eclipse for Java unironically
LoL, I’ve spent much more time configuring vscode.
Vi editors improved my minimalism
4:43 how does he move along references ? Need Help !!
i kinda dislike vim default keybindings, but i feel like if i change any bindings, then i wouldnt be able to neither do stuff at other places whenever the vim is required, nor be ok at using non-vim editors because i would get annoyed at missing all the vim goodness. so ill just stick to default intellij keybindings which are easy to get on both vscode and ij and just zoop with its double shift quick goto and actions and alt+j multiselect similar
I can't find a easy way to do project level find and replace. So I'm kinda switching between neovim and vscode 😅
telescope
@@ThePrimeTimeagenI thought it only searched for file names
@@gritcrit4385 nope! Telescope can search through files, buffers, strings (like a grep), help documentation, keymaps, quick fix lists… just about anything. It’s a fairly generic use tool!