Live data from Hacker News

LazyVim

lazyvim.org

201–210 of 537 posts

Re: LazyVim

#201

I feel like I should be the kind of person who prefers eMacs over vi(m), because I've always been a hotkey maniac. I'm actually not though at all, and I much prefer the simplicity of vim. I already have way too many hotkeys lingering in my brain, especially since I played the game Age of Empires II. I don't play many games these days, and I certainly don't use their hotkeys (I play exclusively on consoles these days,…

I've had several people recommend me their IDEs or some new text editor from time to time by telling me that the editor supports Emacs style keybindings assuming that is the main difference between editors. I've never used emac's native keybindings, nor do I use vim's since I don't use qwerty. While my custom keybindings are something I would not want to give up they can be replicated in any other editor that provide…

> people recommend me their IDEs or some new text editor from time to time by telling me that the editor supports Emacs style keybindings assuming that is the main difference between editors

I get that too but with Vim. People think Vim is just about the controls because all they know about Vim is the :q joke. No, that IDE's Vim plugin doesn't cut it, because unfortunately it comes with an IDE and its distracting overloaded UI, weird tab switching behaviour, absolutely infuriating popups and other annoyances.

Vim being just a really flexible and fast editor with a mostly empty status line as the entire user interface is a feature.

Re: LazyVim

#202
post #85
post #83

Earlier quoted context omitted.

Did you try LazyVim or any other neovim distro? Seems like you're complaining about configuring neovim from scratch, which is that pain that neovim distros aim to remove

Yes I did. And they work fine, until you need to do that one thing (e.g. "Set up Black to format on save"). Now you are back in that world of pain of figuring out which plugin needs to be installed/configured, only now you are figuring out someone else's way of doing it.

I think you're going about the wrong way if you're reaching to plugin for every simple thing in vim. Granted, I will say that vim has steep learning curve, it kinda gives you the power to do your _own_ way which is probably why you're seeing people do their own way. Also, you sort-of have to shift your mindset to embrace unix/shell as your IDE. But definitely reach out to other tools if it's not your cup of tea. Like many others have said, if you're trying to force it into something it's not then you're going to have a miserable time.

As for your e.g. it would be a simple autocommand to run black that's installed in your machine on buffer write event in your neo/vimscript.

`autocmd BufWritePost *.py !black %`

Re: LazyVim

#203
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 am using mostly default settings on my neovim setup for most plugins.

I can't do much with vscode before also install tons of plugins and eventually setting them up. The only major difference to me is a central marketplace for vscode plugins instead of relying on github search engine+recommendations and being subject to telemetry I don't want.

Re: LazyVim

#204
post #3

Earlier quoted context omitted.

I find that any IDE-type setup in vim causes vim to lose the most important thing, speed. If your movements slow down because of too many plugins, the experience is far worse than in a normal non-modal IDE.

> I find that any IDE-type setup in vim causes vim to lose the most important thing, speed. If your movements slow down because of too many plugins, the experience is far worse than in a normal non-modal IDE. Um… the word any is doing a lot of work in this sentence. I never had this problem on a 7 year-old iMac. I tried using VS Code on the same machine with just a few plugins on small projects and because it's an El…

I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.

I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?

https://github.com/LunarVim/LunarVim/discussions/3359

Re: LazyVim

#205
post #148

Earlier quoted context omitted.

> Was that expressly written to parody Vim? Yes. The advice to turn the yoke upside down is supposed to reference remapping Caps Lock to Escape, without which Vim destroys your pinky on a standard keyboard. But it's the choice of professionals, so what can we do?

Trick for those wanting caps lock to be compose instead: ctrl-c also works as escape, and has historically been slightly faster due to sidestepping the escape timeout.

Wow super useful, didn't know that.

EDIT: removed comment about cursor behavior of ctrl-c, which comes from my vimrc config ^^ Turns out I learned that long ago, but never used it :-D

Re: LazyVim

#206
post #160
post #148

Earlier quoted context omitted.

> Was that expressly written to parody Vim? Yes. The advice to turn the yoke upside down is supposed to reference remapping Caps Lock to Escape, without which Vim destroys your pinky on a standard keyboard. But it's the choice of professionals, so what can we do?

I'm playing into the joke here, but on most terminals, alt + will actually be sent to the program as + key. You can use this to avoid pressing escape in Neovim.

Interesting tip too! Need to find the right combination however, I noticed that Alt-L might be a good one (no side effect it seems).

Re: LazyVim

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

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.

Re: LazyVim

#208
post #55

Best protip I heard about (n)vim customization: use git branches when you want to switch between different configurations. Eg something like: - vanilla/default - minimal - fancy depending on what you want to deal with. If I go months between using all these plugins I forget what they do and what changed and it’s just noisy distractions that invariably lead me to open my init.lua file rather than what I actually had i…

you can also use $NVIM_APPNAME if you want a more "full" switch between configurations. especially helpful for trying/switching between distributions (i use it for switching between my own config and lazyvim). basically, it modifies the paths where neovim looks for config and data files on startup:

config path: $XDG_CONFIG_HOME/nvim/ -> $XDG_CONFIG_HOME/$NVIM_APPNAME/

data path on Windows: $LOCALAPPDATA/nvim-data/ -> $LOCALAPPDATA/{$NVIM_APPNAME}-data/

https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME

Re: LazyVim

#209

Earlier quoted context omitted.

Setting up vim with IDE features takes an hour maximum + 2 minutes per additional language. If that is too much for you, you could have used any of the various vim/nvim distributions with the features already there. You could have even used Doom Emacs with vim keys . If you don't want to use vim, I do not mind whatsoever, but if you put in a bit of effort the solution to your problems would appear.

Sure, it's one hour if you did that already 20 times and you know the ecosystem. An hour is barely enough to go through the vimtutor which itself is pretty basic (aka you won't get far with it, so you need to keep learning and practicing). If you are a vim newbie, it takes a lot of time to figure out you need plugins, then figure out how to install plugins, then what's the difference between plugin installers, findin…

I think it takes at least one month to get into vim, let alone mastering any of the plugins, and afterwards you keep learning every day.

IMO this is not due to the difficulty of installing plugins (which is becoming easier and easier), but rather to embrace the vim "philosophy".

Many think that VSCode is better because easier to use and has more features. However I think this is because they don't use any advanced features of VSCode either, only the glaring obvious ones.

Re: LazyVim

#210
post #99

Earlier quoted context omitted.

FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. It also does this for every other language I write in. I have collected my config over the past several years, but I pretty rarely encounter errors with it. It requires no additional dependencie…

This is the problem though: if you come to Neovim, and ask "what is the best formatter/linter" someone will tell you "use null-ls". Then a dozen others will say "don't use null-ls, it's been deprecated, use efm-langserver". OK, how do I set up efm-langserver with Neovim? Good luck! You could probably use a plugin, or maybe not. You'll need a way to install LSP servers. nvm-lsp-installer? Nope,that's also deprecated,…

So basically your problem is feeling insecure because other people do different choices.

I didn't care following all the trends, my setup use coc.nvim[1] and I don't have any problem with that. I don't care about black, I am fine writing python stuff without it.

Your setup doesn't have to be complicated because others is.

[1] which is still maintained by the way.

Post reply on HN