Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LazyVim

lazyvim.org

Post reply on HN
Print view View original

101–110 of 537 posts

Re: LazyVim

#101

Post by TonyStr »

stevebmark wrote: post #82

What was the name of the original Vim magic-auto-default setup project? I wish I could remember it! There used to be so many Vim questions on Stackoverflow from people who installed Vim ________ (?) and had no idea what it did. The advice was always: "Stop using that, and learn Vim." This project smells like that. There are two types of Vim users: 1. "Stop trying to make Vim and IDE with all your fancy plugins, learn…

I would argue vim's cryptic commands like q/, gg, ciw, etc. are anything but verbose. Especially compared to gui editors where similar actions are achieved by clicking through menus.

Your example of commands is a bit odd; I've used many editors without knowing how to access search/command history without that being a detriment to my usability of the editor. If your argument is that one needs a high degree of understanding of vim for it to be useful (more so than IDEs), then I have to disagree. Vim motions alone skyrocket productivity. Anything you can do with multiple cursors, can be done with substitution, repeat motions, block select, macros, etc. Then there are always plugins, should the built in features not satisfy.

Re: LazyVim

#102

Post by eikenberry »

danjac wrote: post #78

I'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…

An alternative to Neovim or VScode that might be worth checking out is Helix (https://helix-editor.com/). It is a Vim/Kakoune inspired editor that is really starting to hit its stride. I haven't used it extensively yet, but I'm testing using it for development now and am thinking of switching to it full time. It maintains the minimalism of (Neo)Vim while coming with a great builtin setup like VScode.

To get a feel for its development status I recommend reading their news post for their 23.03 release.. https://helix-editor.com/news/release-23-03-highlights/

Re: LazyVim

#103

Post by baq »

danjac wrote: post #78

I'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 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.

I’ve done that a couple years ago after ~15 years of happy vimming. Still yearning for the text manipulation language combined with macros, but all the other gains significantly outweigh the worse editing capabilities.

Re: LazyVim

#104

Post by weaksauce »

danjac wrote: post #78

I'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…

neovim extension + vscode is a great pairing. full neovim in normal and visual mode but you can call out to vscode anytime you want in those modes and you also get neovim extensions too. it's great and fast... worth a try.

Re: LazyVim

#105

Post by godelski »

mathisfun123 wrote: post #43
godelski wrote: post #39

I know it sounds like a pain, but I really am a big advocate for learning how to customize vim (or emacs) yourself. These are great places to start, but the power of terminal editors is that they cater to you at a very personal level. The problem with "IDEs" isn't that they are bulky, it is that they railroad you into doing something a very specific way. Terminal emulators put the custom configuration in your face be…

> Turn it into a game if you want. some of us don't have time to play games? i mean definitely used to when i was a kid but now i have lots of deadlines and little enough time to play games with my human friends let alone with my editor. > make the editor __yours__ a good tool is useful immediately and has the potential to be personalized. i mean imagine how little carpentry would ever get done if every hammer, drill…

> some of us don't have time to play games?

So don't. See the next part you quoted from me. But also, IIRC you're in grad school (too), right? Little time is kinda part of the deal. It sucks, I know.

But like others are saying, vim is useful right away. But I do disagree immensely with your premise. A good tool has no requirements to be immediately useful. There's lots of carpentry tools that require training to use, let alone use well. You can be good at vim or emacs in 30 minutes after using vim tutor, but like all specialty tools, it takes time. And that time really comes from using it, not from sitting down and reading about it. The same way you learn how to use a jigsaw, experience. Every carpenter has their custom set of jigs and way of organizing. Same is true for any engineer, or realistically any profession. Whatever it is that makes __you__ most effective, that's what you should do. Maybe that isn't vim at all and that's okay. I never even implied you needed vim, I'm just saying you should customize your environment. And like I implied, start with something someone else has put together, but learn to customize it to you. That'll take time and that's okay. There's no difference in using one of these than just using someone else's dotfiles. But making your own dotfiles is going to make you better in the long run because your tools will match you.

Re: LazyVim

#106

Post by danjac »

eikenberry wrote: post #102
danjac wrote: post #78

I'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…

An alternative to Neovim or VScode that might be worth checking out is Helix ( https://helix-editor.com/ ). It is a Vim/Kakoune inspired editor that is really starting to hit its stride. I haven't used it extensively yet, but I'm testing using it for development now and am thinking of switching to it full time. It maintains the minimalism of (Neo)Vim while coming with a great builtin setup like VScode. To get a feel…

Helix is quite nice, with some sensible defaults and an easier setup. The keybindings take a bit of getting used to if you are coming from it with years of vim muscle memory, but kind of make more sense when you think about it (select+action vs action+select). It's still rough around the edges but one to keep an eye on.

Re: LazyVim

#107

Post by pkulak »

thatxliner wrote: post #91

How does this compare to https://github.com/AstroNvim/AstroNvim

Not as much stuff baked in. They are very similar. AstroNvim uses Lazy as the package manager as well.

Re: LazyVim

#108

Post by joshka »

I dallied in this briefly, but couldn't get a good rust setup exactly how I liked, so went back to vscode pretty quick. Perhaps there's a good lazy+rust guide somewhere? I ran into the usual sorts of problems of some random plugin with instructions for how to install it in some other plugin manager for nvim, which means you have to learn two plugin managers and both their underlying concepts in order to port the config.

Re: LazyVim

#109

Post by aulin »

mathisfun123 wrote: post #43
godelski wrote: post #39

I know it sounds like a pain, but I really am a big advocate for learning how to customize vim (or emacs) yourself. These are great places to start, but the power of terminal editors is that they cater to you at a very personal level. The problem with "IDEs" isn't that they are bulky, it is that they railroad you into doing something a very specific way. Terminal emulators put the custom configuration in your face be…

> Turn it into a game if you want. some of us don't have time to play games? i mean definitely used to when i was a kid but now i have lots of deadlines and little enough time to play games with my human friends let alone with my editor. > make the editor __yours__ a good tool is useful immediately and has the potential to be personalized. i mean imagine how little carpentry would ever get done if every hammer, drill…

> i mean imagine how little carpentry would ever get done if every hammer, drill, and tablesaw needed to be personalized

This kind of metaphor gets thrown around so often in this context. The editor is not your hammer, it's not your drill, it's your entire workshop.

Re: LazyVim

#110

Post by godelski »

mathisfun123 wrote: post #53
lawn wrote: post #50

Earlier quoted context omitted.

> a good tool is useful immediately and has the potential to be personalized. Vim is useful immediately! I use it without customization all the time when I ssh into a new system for instance.

> I use it without customization i do too - all i know is :bn, :bp, b, e, ciw, v and shift+v (and :wq) and it's all i've known for over 10 years. i use the arrow keys on the keyboard too! fingers crossed it'll last me the rest of my career too. but i mostly use clion/pycharm and there the defaults are reasonable and the ux of shift+shift is absolutely unbeatable.

I'll give you an easy useful command: smart completion. In insert mode use then for a word or for a line, or for a directory path. You can repeat them because it is contextual. See `:h ins-completion`.

Also, get away from the arrow keys. And use for escape. But it is also okay if you don't like vim. If you want to learn, there's a community out there and we're happy to help, but if you don't then that's okay too. You just do you and that's all cool :)

Post reply on HN