Live data from Hacker News

LazyVim

lazyvim.org

331–340 of 537 posts

Re: LazyVim

#331
post #156
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…

>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 spend precious hours fixing obscure issues in Lu Can't agree with this at all. I don't think I've spent more than an hour in total setting up my vim config back in…

> Most of the plugins have docs that can be accessed via (neo)vim itself. Usually you can find all information there.

This was something which took some time for me to notice. There are some plugins which have the best documentations I have ever seen, but you need to read it from the Vim.

Example of coc.nvim: https://github.com/neoclide/coc.nvim/blob/master/doc/coc.txt and https://github.com/neoclide/coc.nvim/blob/master/doc/coc-con... and https://github.com/neoclide/coc.nvim/blob/master/doc/coc-api...

Re: LazyVim

#332
I don't get the [Neo]Vim IDEs dichotomy. VS Code and IntelliJ both have excellent Vim plugins.

Re: LazyVim

#333
post #322

Earlier quoted context omitted.

[flagged]

Do you still use a QWERTY keyboard? Or have you just been beaten over the head with them so long that Stockholm syndrome is super strong?

Did you read my original comment? I literally mentioned QWERTY as another example of backwards compatibility screwing everyone over.

I use QWERTY because I have to, I don't like it and I can't do much about it in practice. People frequently defend Vi's HJKL vehemently - just like - if I'm not mistaken - you, presenting it as a superior option for some reason.

Re: LazyVim

#334
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…

Did you actually try LazyVim? It makes this whole process a lot easier, with pre-cooked extras for most popular languages.

Yes I did, and no it didn't really help. Sure it was a much slicker starting point, but when I needed to do a bit more (ie. configure a formatter) it just added more obfuscation than anything. The "pre-cooked" part does help with setting up linting, but formatting...you're kind of on your own (if you search the source you can find an example with prettier but you will still need to add your own integration for anything else).

Re: LazyVim

#335
post #266

Earlier quoted context omitted.

I do roughly this too, except my vimrc is about 8 lines. I type it out from memory every time I use a new machine.

Would you mind sharing it? Im just getting to grips with vim so any pointers towards some simple improvements would be much appreciated.

Sure:

  set ts=4
  set sw=4
  set softtabstop=4
  set expandtab
  set hlsearch
  set incsearch
  set wildmode=longest,list
OK, only 7 lines then :)

Basically: tabs are 4 spaces, searching works better, and tab completion works like bash.

Re: LazyVim

#336
I have tried most of these out of the box neovim stuff and they do work for the most part but as soon as you want to tweak things it's not as easy. Besides that sometimes plug-ins can just break due to a bad merge and that can just break some core feature and now you are stuck either finding a fix or just go back and use VSCode

Re: LazyVim

#337
Most people miss "Vim Is More than Just an Editor." The Vim Language, its motions, and its modes will make you a better programmer and writer. If you invested in the vim language early on, you can use it on each editor, browser, and other apps. This has nothing to do with the editor yet – these are universal and available. For example, there's VSVim for VSCode, IdeaVim for the JetBrains products, Vintage Mode for Sublime, and so on. But there are also Browser extensions like Vimium or Firenvim, and Gmail even adopted some of Vim's shortcuts for navigation (j, k for moving, g for jumping).

Everyone who types on a computer eight hours a day should learn the Vim language. Yes it's hard initially, but that's the case with everything new and different. But getting better every day and having more fun coding or writing should be motivation enough. Also, imagine, if you work over a decade, how many times you had to learn a new editor (notepad++, atom, eclipse, ...) some of which do not exist anymore. If you once learned the vim language, you are getting stronger. There is a reason the editor has existed since the eclipse of programming.

The Vim grammar is exceptional, as spoken language has verbs, subjects, and objects, as does the Vim language. The grammar has different verbs, to begin with. Copying (or yanking) in Vim with y, deleting with d, pasting with p, changing with c, and so on.

You can also see in the comments here people fight over Vim and VSCode, where the natural beauty is the language behind Vim. If you do not want to configure and customize your own, use VSCode and add the Vim extension. But if you're going to get better at your job, you should try the Vim language.

Once mastered, you edit text at the speed of thought. Sounds cheeky, but it's true for me. Instead of thinking, "I want to edit that word," my fingers jump to it and change it with a few keystrokes.

I wrote more on https://www.ssp.sh/blog/why-using-neovim-data-engineer-and-w... in case you are interested.

Re: LazyVim

#339
post #132

Am I the only one using vanilla vim with a minimal configuration file ( Very easy to setup. Moreover, when I'm on a different computer and open (vanilla) vim without any configurations. I know that everything is more or less the same as my default vim environment. I think it's not that hard to learn developing in the default vim environment, with some minor tweaks. Also related, How to Do 90% of What Plugins Do (With…

Nothing says someone doesn't grok vim like a permanent nerdtree pane.

It helps though with remembering where you are in your codebase. Rather than cluttering my brain with the info that Nerdtree provides, I can instead use the extra brainpower for other things.
Post reply on HN