[deleted]
LazyVim
391–400 of 537 posts
Re: LazyVim
#392I really wish I could just put a native neovim or vim text editor inside VSCode and call it a day. I absolutely love the lightning fast experience of editing with vim. When I know exactly what I want to do, I feel like I just ripped a line of spice and piloted a trade vehicle across Frank Herbert's universe. But a lot of my job is exploring a code base and trying to figure out what the hell is going on, and I have to…
Have you tried the vscode-neovim extension? That's basically what it does.
Re: LazyVim
#393I really wish I could just put a native neovim or vim text editor inside VSCode and call it a day. I absolutely love the lightning fast experience of editing with vim. When I know exactly what I want to do, I feel like I just ripped a line of spice and piloted a trade vehicle across Frank Herbert's universe. But a lot of my job is exploring a code base and trying to figure out what the hell is going on, and I have to…
Have you looked at the "VSCode Neovim" extension? It uses a native neovim editor in the background (instead of just emulating VIM like VSCodeVim), so the editing experience is the same as native vim.
Re: LazyVim
#394the original vim has always been my daily editor, yes I did spend time learning it along the way and it worth every minute I invested, it does everything vscode or other IDE can do for me. typing while moving mouse and clicking here and there on an IDE is not as productive comparing focusing on keyboard typing, to say the least.
the beauty is that I can use it on any servers too.
Re: LazyVim
#395I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
Vim, the program, I find useful in limited cases. Vim, the keybindings, I find I try to use everywhere -- from the browser to every IDE I ever work in.
Re: LazyVim
#396I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
I’ve felt similarly, and really wanted to switch to VSCode. But it gives each pane its own set of tabs, while Vim has a single set of “tabs” (buffers) and multiple panes within it.
I’ve been using N/Vim for 25 years, and even after trying for a week or two, I just can’t get comfortable with VSCode’s way of doing it.
Re: LazyVim
#397I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
I think learning vim was very worthwhile for me cause I now use vim bindings if it's supported, but yeah vscode was getting slower for me the past few months and I decided to try neovim again and man so many things have changed since the last time I tried it with the new Lua config. I feel like it'll take me a day to recreate a config im satisfied with and it'll probably have a few bugs too after using it for a while.
Re: LazyVim
#398I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
If you want IDE like features, then of course an IDE is a better choice. I've never understood why people and to extend vim to try to make it half of an IDE.
For many people, it's because the choices for an IDE are all dog slow, and configuring a few plugins for their editor of choice provides a close-enough experience to strike the balance they are looking for.
So, no, an IDE is not a better choice for everyone who want's "IDE like features". It is for some, but not everyone.
Re: LazyVim
#399I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
I’ve felt similarly, and really wanted to switch to VSCode. But it gives each pane its own set of tabs, while Vim has a single set of “tabs” (buffers) and multiple panes within it. I’ve been using N/Vim for 25 years, and even after trying for a week or two, I just can’t get comfortable with VSCode’s way of doing it. https://github.com/microsoft/vscode/issues/143024
I find the same.
Vim has some core concepts that are unique and (for those of us who adopt them) very sticky.
My entire career has been spent trying out IDEs every few years in hope of switching, dating back to Eclipse. I always try their vim modes too.
But the reality is that the core editing experience in vim is so central to how I work that I can never manage it.
I like features, and I have no love for arcane configuration of plugins. Yet to this day I've found nothing better for me than vim.
Re: LazyVim
#400Earlier quoted context omitted.
It does not break down. Chainsaw is very good at doing chainsaw things. If what you need to do is cut down bunch of trees then chainsaw is exactly what you need. No one in their right minds would start with a knife and start building it into a saw and then attach a motor to motorize it. Mind you we were carving a bowl, but as per Internet argument you completely dismissed the use case and inserted your own. If VSCode…
The problem is that Vim can be used to create config files and source code files among other things. VS Code can be used for very much the same things. The output of both tools is practically the same thing. The niche of things Vim can do and VS Code can't is tiny and constantly decreasing.
You can run Neovim on a remote server through ssh. I think that's the main difference