skeleton.nvim
kickstart.nvim
skeleton.nvim | kickstart.nvim | |
---|---|---|
12 | 285 | |
5 | 15,275 | |
- | 9.4% | |
9.0 | 9.1 | |
11 days ago | 3 days ago | |
Lua | Lua | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
skeleton.nvim
-
I love this bastard
here is my config if you want to take a look (but it's using lsp-zero v1 and now they have a v2, I'm still planning on migrating to it)
-
Can anyone recommend a good github dotfiles repos for neovim that uses LazyVim as it's plugin manager?
maybe my dotfiles could help you? not using tabs unfortunately.
-
Looking for feedback on my neovim config with lazy
this is just what :h vim.pretty_print does
-
Some treesitter related plugins fail when bootstrapping with packer
I changed the plugin initialization to work like you mentioned (using the lazy.nvim init function) and now it works. only problem is that this feels a little bit bloated, not sure if there's a way to work around this. but for now it's good enough
-
How can I set an autocommand that only initializes for the current buffer for lsp on_attach?
Here is my full configuration if needed: https://github.com/brunobmello25/skeleton.nvim/tree/add-vtsls (branch add-vtsls)
-
LSP server with tsserver extremely slow and sometimes even timing out
I have showed some of my config files, but I have also just pushed a branch to my nvim config repo with the current configuration showed on the video. Here is a link to the repository on the specified branch.
-
Can't figure out why my fonts are not rendering properly
And my neovim config: https://github.com/brunobmello25/skeleton.nvim
-
How can I setup eslint lsp to only attach if eslint config exists and fallback to prettier formatter if it doesn't?
Sorry for the wall of text. Here is my current configuration if it's of any use: https://github.com/brunobmello25/skeleton.nvim
-
Help implementing prettier formatter as a "fallback" for when there is no eslint attached?
Currently, here is how I setup my neovim to format with eslint: https://github.com/brunobmello25/skeleton.nvim/blob/main/lua/skeleton/lsp/languages/typescript.lua
-
telescope styles broke after packerSync?
Here is my current config, branch main
kickstart.nvim
-
From JetBrains to VSCode to NVIM: Why I Made the Switch
Out of the box it offers almost nothing, but after 7 years of development I like that. I love the idea of customizing to my needs my IDE, so with the help of kickstart.nvim I have with 1 minute of installing and 10 extra minutes of configuration a complete IDE.
-
Using a venv with Neovim's Python LSP
I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.
-
I Learned Neovim In A Weekend
First thing I did was get kickstart.nvim. I had heard it was extremely useful (and it was). It was very easy to install. I start reading through init.lua, and it told me to run :Tutor, which is almost 1,000 lines of learning how to use Neovim, to which I obviously ran that command and started reading. Obviously, it takes a bit of time to complete :Tutor, but it's well worth it. "hjkl" wasn't too hard to get used to, also repeating motions by using numbers was useful, such as using '5dd' to delete 5 lines. I highly suggest reading this file, especially since I didn't really know about the different modes, which is probably why I failed to switch the other times. You would start writing your code, then Neovim would say that it can't find that command, you would accidently type an i and then start typing, and so on, it was a nightmare. For those that don't know the modes, here is each mode and how to get between them.
- Kickstart.nvim: Single file launch point for a personal nvim config
-
Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
I also suggest against using distributions. Instead of learning how to configure nvim itself you're learning to configure that specific distro.
I suggest to take someone's lua config and start from there. Kickstart.nvim is a good one: https://github.com/nvim-lua/kickstart.nvim
- It’s been an hour and I have made no progress
-
Do I need NeoVIM?
1) the option I wouldn’t chose, use Kickstarter. It’s a minimal starter config, using a single init.lua that helps you build a config slowly. https://github.com/nvim-lua/kickstart.nvim
-
ready to use neovim for web development (frontend) - beginners
I highly recommend Lazyvim for if you want to have a VSCode (ish) like experience that still exposes you to configuring in Lua. Or Kickstart.nvim if you want a more "from scratch" experience
-
Search commands slow in neovim but fast in vim
In case it is helpful, I am using kickstart.nvim with only minor modifications.
-
Kickstart.emacs Starter kit for Gnu Emacs
One of the project goals is to become something like kickstart.nvim. Or, to be a reference if someone doesn't know how to do something.
What are some alternatives?
nvim-vtsls
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
nvim-starter - Neovim example configuration. To help you start in your journey
nvim-lua-guide - A guide to using Lua in Neovim
neovim - My neovim config
LazyVim - Neovim config for the lazy
lazy.nvim - 💤 A modern plugin manager for Neovim
quick-scope - Lightning fast left-right movement in Vim
KotlinLanguageServer - Kotlin code completion, diagnostics and more for any editor/IDE using the Language Server Protocol
dot - ☕️ My Dot Files
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable