HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nvim-lua
kickstart.nvim
Lua2021–2026
nvim-lua / kickstart.nvim

kickstart.nvim

A launch point for your personal nvim configuration

Explore on GitHubRead Hacker News discussions
30Distinct people
30Mentions
1Explicit recommenders
31.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A launch point for your personal nvim configuration

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I went from VSCode back to vim via Neovim and it works great. I am setup for go and lua. I took a base config called kickstart and removed things I didn't need. Then I added…

dizhn used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year30 dated mentions

Observed mentions: 2021-10-25 13:08:39 UTC to 2026-05-23 15:55:20 UTC.

0369122021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 3 submissions, 8 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1138
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC927
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

11 sources
bamazizi·Nov 5, 2023
I spend a lot time inside vim/neovim on daily basis. I do have vscode open as well but it's mostly for referencing or file exploration on repos I'm not familiar with. Building a mental and muscle memory is tough but it requires grinding. You have to put in the time! It took me months! My biggest mistake was starting and playing around with configurations and plugins for days/weeks and constantly having a broken environment! Configuration hell is the worst path to get into neovim! Start with the starter kit but avoid going into installing 10s of plugins, custom key-mappings and themes until you have learned the fundamental of motions, navigations and editing. Starter kit: https://github.com/nvim-lua/kickstart.nvim
In Effective Neovim: An Instant IDE [video]
Exuma·Sep 3, 2023
Ok I got you mane.. you have 2 solutions. By the way, there is a sort of "common" set of configurations that probably 90% of people have in their vim config, like turning off the bell and stuff. Obviously there are exceptions because those people know what they're doing, but my point is that don't give up on it until you at least try a common config to remove a lot of the basic annoyances. Solution 1: Add this to your vimrc. This will make it so when going up and down, wrapped lines are properly interpreted and not skipped ``` " better up and down map j gj map k gk ``` Solution 2: If you want to make it where the cursor literally goes ANYWHERE in the document, including in space that doesn't even exist, do this below. I used this mode for a very long time and it's amazing. I only switched recently just to try something new to see if I lik
Read the rest
e it more, and right now I'm just 50/50 on if its better or not ``` " allow cursor to go anywhere set virtualedit=all ``` Lastly, try using `vimtutor` from terminal and practice commands right there in your terminal. And, if by "slow" you are talking about literal performance, try Neovim. Neovim is basically a fork of nvim that gets rid of vimscript (but still allows it if you want to use it) and instead implements Lua, which is an extremely (the fastest, actually) scripting language. (The other comment you asked about was a Neovim lua configuration which does the same thing as the vimscript version). Part of the Neovim idea is that they also set a lot more "sane" default config thats more modern. The best part about Neovim is that it supports LSP's in a much better way, so you can complete VS-Code like IDE experience, rather than relying on a complex array of plugins. If you decide to do that, check out lsp-zero for the easiest setup possible. If you decide to give neovim a shot, I would 100% recommend using this: https://github.com/nvim-lua/kickstart.nvim I recently transferred 10+ year vim config to lua and neovim, and I saw people recommending this over and over. Because I wasnt familiar with it I thought "I dont need that, i want to start fresh". Well after doing that for nearly a month, I realized how good kickstart is, it REALLY is quite good, and does lots and lots that you would want without doing too much. I didnt use it, but i took tons of inspiration from it for setting up LSPs. Let me know if you have any questions I'd love to not lose vim friend over something stupid like moving on long lines.
In How to type “blimpy” in Emacs [video]
dizhn·Jul 17, 2023Recommendation phrase
I went from VSCode back to vim via Neovim and it works great. I am setup for go and lua. I took a base config called kickstart and removed things I didn't need. Then I added things I do need. As for the community, the channel on Matrix is one of my favorite communities. Whenever I needed help, it came instantly and with precisely what I need. (They must be getting the same things a lot). They never suggested I use a big plugin to solve a little problem as far as I can remember. All in all it looks like we had a wildly different experience. I suspect the real issue is that I like to work with vim a million times than I did with vscode. You might me biased the other way. I feel better on the command line and it's amazing how much people have figured out already to make things run well and look nice. Kickstart nvim: https://github.com/nvim-
Read the rest
lua/kickstart.nvim
In LazyVim

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.