[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-70596":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},70596,"kickstart.nvim","nvim-lua\u002Fkickstart.nvim","nvim-lua","A launch point for your personal nvim configuration",null,"Lua",30798,46340,137,18,0,42,85,285,126,45,"MIT License",false,"master",true,[],"2026-06-12 02:02:35","# kickstart.nvim\n\n## Introduction\n\nA starting point for Neovim that is:\n\n* Small\n* Single-file\n* Completely Documented\n\n**NOT** a Neovim distribution, but instead a starting point for your configuration.\n\n## Installation\n\n### Install Neovim\n\nKickstart.nvim targets *only* the latest\n['stable'](https:\u002F\u002Fgithub.com\u002Fneovim\u002Fneovim\u002Freleases\u002Ftag\u002Fstable) and latest\n['nightly'](https:\u002F\u002Fgithub.com\u002Fneovim\u002Fneovim\u002Freleases\u002Ftag\u002Fnightly) of Neovim.\nIf you are experiencing issues, please make sure you have at least the latest\nstable version. Most likely, you want to install neovim via a [package\nmanager](https:\u002F\u002Fgithub.com\u002Fneovim\u002Fneovim\u002Fblob\u002Fmaster\u002FINSTALL.md#install-from-package).\nTo check your neovim version, run `nvim --version` and make sure it is not\nbelow the latest\n['stable'](https:\u002F\u002Fgithub.com\u002Fneovim\u002Fneovim\u002Freleases\u002Ftag\u002Fstable) version. If\nyour chosen install method only gives you an outdated version of neovim, find\nalternative [installation methods below](#alternative-neovim-installation-methods).\n\n### Install External Dependencies\n\nExternal Requirements:\n- Basic utils: `git`, `make`, `unzip`, C Compiler (`gcc`)\n- [ripgrep](https:\u002F\u002Fgithub.com\u002FBurntSushi\u002Fripgrep#installation),\n  [fd-find](https:\u002F\u002Fgithub.com\u002Fsharkdp\u002Ffd#installation)\n- [tree-sitter CLI](https:\u002F\u002Fgithub.com\u002Ftree-sitter\u002Ftree-sitter\u002Fblob\u002Fmaster\u002Fcrates\u002Fcli\u002FREADME.md#installation)\n- Clipboard tool (xclip\u002Fxsel\u002Fwin32yank or other depending on the platform)\n- A [Nerd Font](https:\u002F\u002Fwww.nerdfonts.com\u002F): optional, provides various icons\n  - if you have it set `vim.g.have_nerd_font` in `init.lua` to true\n- Emoji fonts (Ubuntu only, and only if you want emoji!) `sudo apt install fonts-noto-color-emoji`\n- Language Setup:\n  - If you want to write Typescript, you need `npm`\n  - If you want to write Golang, you will need `go`\n  - etc.\n\n> [!NOTE]\n> See [Install Recipes](#Install-Recipes) for additional Windows and Linux specific notes\n> and quick install snippets\n\n### Install Kickstart\n\n> [!NOTE]\n> [Backup](#FAQ) your previous configuration (if any exists)\n\nNeovim's configurations are located under the following paths, depending on your OS:\n\n| OS | PATH |\n| :- | :--- |\n| Linux, MacOS | `$XDG_CONFIG_HOME\u002Fnvim`, `~\u002F.config\u002Fnvim` |\n| Windows (cmd)| `%localappdata%\\nvim\\` |\n| Windows (powershell)| `$env:LOCALAPPDATA\\nvim\\` |\n\n#### Recommended Step\n\n[Fork](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fget-started\u002Fquickstart\u002Ffork-a-repo) this repo\nso that you have your own copy that you can modify, then install by cloning the\nfork to your machine using one of the commands below, depending on your OS.\n\n> [!NOTE]\n> Your fork's URL will be something like this:\n> `https:\u002F\u002Fgithub.com\u002F\u003Cyour_github_username>\u002Fkickstart.nvim.git`\n\nYou likely want to remove `nvim-pack-lock.json` from your fork's `.gitignore`\nfile too - it's ignored in the kickstart repo to make maintenance easier, but\nit's recommended to track it in version control (see `:help vim.pack-lockfile`).\n\n#### Clone kickstart.nvim\n\n> [!NOTE]\n> If following the recommended step above (i.e., forking the repo), replace\n> `nvim-lua` with `\u003Cyour_github_username>` in the commands below\n\n\u003Cdetails>\u003Csummary> Linux and Mac \u003C\u002Fsummary>\n\n```sh\ngit clone https:\u002F\u002Fgithub.com\u002Fnvim-lua\u002Fkickstart.nvim.git \"${XDG_CONFIG_HOME:-$HOME\u002F.config}\"\u002Fnvim\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\u003Csummary> Windows \u003C\u002Fsummary>\n\nIf you're using `cmd.exe`:\n\n```\ngit clone https:\u002F\u002Fgithub.com\u002Fnvim-lua\u002Fkickstart.nvim.git \"%localappdata%\\nvim\"\n```\n\nIf you're using `powershell.exe`\n\n```\ngit clone https:\u002F\u002Fgithub.com\u002Fnvim-lua\u002Fkickstart.nvim.git \"${env:LOCALAPPDATA}\\nvim\"\n```\n\n\u003C\u002Fdetails>\n\n### Post Installation\n\nStart Neovim\n\n```sh\nnvim\n```\n\nThat's it! `vim.pack` will install all the plugins from your config. Use\n`:lua vim.pack.update(nil, { offline = true })` to inspect plugin state and\n`:lua vim.pack.update()` to fetch updates (`:write` applies updates, `:quit`\ncancels them).\n\n#### Read The Friendly Documentation\n\nRead through the `init.lua` file in your configuration folder for more\ninformation about extending and exploring Neovim. That also includes\nexamples of adding popularly requested plugins.\n\n> [!NOTE]\n> For more information about a particular plugin check its repository's documentation.\n\n\n### Getting Started\n\n[The Only Video You Need to Get Started with Neovim](https:\u002F\u002Fyoutu.be\u002Fm8C0Cq9Uv9o)\n\n### FAQ\n\n* What should I do if I already have a pre-existing Neovim configuration?\n  * You should back it up and then delete all associated files.\n  * This includes your existing init.lua and the Neovim files in `~\u002F.local`\n    which can be deleted with `rm -rf ~\u002F.local\u002Fshare\u002Fnvim\u002F`\n* Can I keep my existing configuration in parallel to kickstart?\n  * Yes! You can use [NVIM_APPNAME](https:\u002F\u002Fneovim.io\u002Fdoc\u002Fuser\u002Fstarting.html#%24NVIM_APPNAME)`=nvim-NAME`\n    to maintain multiple configurations. For example, you can install the kickstart\n    configuration in `~\u002F.config\u002Fnvim-kickstart` and create an alias:\n    ```\n    alias nvim-kickstart='NVIM_APPNAME=\"nvim-kickstart\" nvim'\n    ```\n    When you run Neovim using `nvim-kickstart` alias it will use the alternative\n    config directory and the matching local directory\n    `~\u002F.local\u002Fshare\u002Fnvim-kickstart`. You can apply this approach to any Neovim\n    distribution that you would like to try out.\n* What if I want to \"uninstall\" this configuration:\n  * Remove your config directory and local data directory (for example,\n    `~\u002F.config\u002Fnvim` and `~\u002F.local\u002Fshare\u002Fnvim`).\n* Why is the kickstart `init.lua` a single file? Wouldn't it make sense to split it into multiple files?\n  * The main purpose of kickstart is to serve as a teaching tool and a reference\n    configuration that someone can easily use to `git clone` as a basis for their own.\n    As you progress in learning Neovim and Lua, you might consider splitting `init.lua`\n    into smaller parts. A fork of kickstart that does this while maintaining the\n    same functionality is available here:\n    * [kickstart-modular.nvim](https:\u002F\u002Fgithub.com\u002Fdam9000\u002Fkickstart-modular.nvim)\n  * Discussions on this topic can be found here:\n    * [Restructure the configuration](https:\u002F\u002Fgithub.com\u002Fnvim-lua\u002Fkickstart.nvim\u002Fissues\u002F218)\n    * [Reorganize init.lua into a multi-file setup](https:\u002F\u002Fgithub.com\u002Fnvim-lua\u002Fkickstart.nvim\u002Fpull\u002F473)\n\n### Install Recipes\n\nBelow you can find OS specific install instructions for Neovim and dependencies.\n\nAfter installing all the dependencies continue with the [Install Kickstart](#install-kickstart) step.\n\n#### Windows Installation\n\n\u003Cdetails>\u003Csummary>Windows with Microsoft C++ Build Tools and CMake\u003C\u002Fsummary>\nKickstart's default config is make-only for `telescope-fzf-native.nvim`.\nIf `make` is unavailable, the plugin is skipped.\n\nRecommended: install `make` (see the chocolatey section below).\n\nIf you want a CMake-only setup, customize `init.lua` in two places:\n\n1. Include `telescope-fzf-native.nvim` when `cmake` is available:\n\n```lua\nif vim.fn.executable 'make' == 1 or vim.fn.executable 'cmake' == 1 then\n  table.insert(plugins, gh 'nvim-telescope\u002Ftelescope-fzf-native.nvim')\nend\n```\n\n2. In the `PackChanged` hook, use CMake when `make` is unavailable:\n\n```lua\nif name == 'telescope-fzf-native.nvim' then\n  if vim.fn.executable 'make' == 1 then\n    run_build(name, { 'make' }, ev.data.path)\n  elseif vim.fn.executable 'cmake' == 1 then\n    run_build(name, { 'cmake', '-S.', '-Bbuild', '-DCMAKE_BUILD_TYPE=Release' }, ev.data.path)\n    run_build(name, { 'cmake', '--build', 'build', '--config', 'Release', '--target', 'install' }, ev.data.path)\n  end\n  return\nend\n```\n\nSee `telescope-fzf-native` documentation for [build details](https:\u002F\u002Fgithub.com\u002Fnvim-telescope\u002Ftelescope-fzf-native.nvim#installation).\n\u003C\u002Fdetails>\n\u003Cdetails>\u003Csummary>Windows with gcc\u002Fmake using chocolatey\u003C\u002Fsummary>\nAlternatively, one can install gcc and make which don't require changing the config,\nthe easiest way is to use choco:\n\n1. install [chocolatey](https:\u002F\u002Fchocolatey.org\u002Finstall)\neither follow the instructions on the page or use winget,\nrun in cmd as **admin**:\n```\nwinget install --accept-source-agreements chocolatey.chocolatey\n```\n\n2. install all requirements using choco, exit the previous cmd and\nopen a new one so that choco path is set, and run in cmd as **admin**:\n```\nchoco install -y neovim git ripgrep wget fd unzip gzip mingw make tree-sitter\n```\n\u003C\u002Fdetails>\n\u003Cdetails>\u003Csummary>WSL (Windows Subsystem for Linux)\u003C\u002Fsummary>\n\n```\nwsl --install\nwsl\nsudo add-apt-repository ppa:neovim-ppa\u002Funstable -y\nsudo apt update\nsudo apt install make gcc ripgrep fd-find tree-sitter-cli unzip git xclip neovim\n```\n\u003C\u002Fdetails>\n\n#### Linux Install\n\u003Cdetails>\u003Csummary>Ubuntu Install Steps\u003C\u002Fsummary>\n\n```\nsudo add-apt-repository ppa:neovim-ppa\u002Funstable -y\nsudo apt update\nsudo apt install make gcc ripgrep fd-find tree-sitter-cli unzip git xclip neovim\n```\n\u003C\u002Fdetails>\n\u003Cdetails>\u003Csummary>Debian Install Steps\u003C\u002Fsummary>\n\n```\nsudo apt update\nsudo apt install make gcc ripgrep fd-find tree-sitter-cli unzip git xclip curl\n\n# Now we install nvim\ncurl -LO https:\u002F\u002Fgithub.com\u002Fneovim\u002Fneovim\u002Freleases\u002Flatest\u002Fdownload\u002Fnvim-linux-x86_64.tar.gz\nsudo rm -rf \u002Fopt\u002Fnvim-linux-x86_64\nsudo mkdir -p \u002Fopt\u002Fnvim-linux-x86_64\nsudo chmod a+rX \u002Fopt\u002Fnvim-linux-x86_64\nsudo tar -C \u002Fopt -xzf nvim-linux-x86_64.tar.gz\n\n# make it available in \u002Fusr\u002Flocal\u002Fbin, distro installs to \u002Fusr\u002Fbin\nsudo ln -sf \u002Fopt\u002Fnvim-linux-x86_64\u002Fbin\u002Fnvim \u002Fusr\u002Flocal\u002Fbin\u002F\n```\n\u003C\u002Fdetails>\n\u003Cdetails>\u003Csummary>Fedora Install Steps\u003C\u002Fsummary>\n\n```\nsudo dnf install -y gcc make git ripgrep fd-find tree-sitter-cli unzip neovim\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\u003Csummary>Arch Install Steps\u003C\u002Fsummary>\n\n```\nsudo pacman -S --noconfirm --needed gcc make git ripgrep fd tree-sitter-cli unzip neovim\n```\n\u003C\u002Fdetails>\n\n### Alternative neovim installation methods\n\nFor some systems it is not unexpected that the [package manager installation\nmethod](https:\u002F\u002Fgithub.com\u002Fneovim\u002Fneovim\u002Fblob\u002Fmaster\u002FINSTALL.md#install-from-package)\nrecommended by neovim is significantly behind. If that is the case for you,\npick one of the following methods that are known to deliver fresh neovim versions very quickly.\nThey have been picked for their popularity and because they make installing and updating\nneovim to the latest versions easy. You can also find more detail about the\navailable methods being discussed\n[here](https:\u002F\u002Fgithub.com\u002Fnvim-lua\u002Fkickstart.nvim\u002Fissues\u002F1583).\n\n\n\u003Cdetails>\u003Csummary>Bob\u003C\u002Fsummary>\n\n[Bob](https:\u002F\u002Fgithub.com\u002FMordechaiHadad\u002Fbob) is a Neovim version manager for\nall platforms. Simply install\n[rustup](https:\u002F\u002Frust-lang.github.io\u002Frustup\u002Finstallation\u002Fother.html),\nand run the following commands:\n\n```bash\nrustup default stable\nrustup update stable\ncargo install bob-nvim\nbob use stable\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\u003Csummary>Homebrew\u003C\u002Fsummary>\n\n[Homebrew](https:\u002F\u002Fbrew.sh) is a package manager popular on Mac and Linux.\nSimply install using [`brew install`](https:\u002F\u002Fformulae.brew.sh\u002Fformula\u002Fneovim).\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\u003Csummary>Flatpak\u003C\u002Fsummary>\n\nFlatpak is a package manager for applications that allows developers to package their applications\njust once to make it available on all Linux systems. Simply [install flatpak](https:\u002F\u002Fflatpak.org\u002Fsetup\u002F)\nand setup [flathub](https:\u002F\u002Fflathub.org\u002Fsetup) to [install neovim](https:\u002F\u002Fflathub.org\u002Fapps\u002Fio.neovim.nvim).\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\u003Csummary>asdf and mise-en-place\u003C\u002Fsummary>\n\n[asdf](https:\u002F\u002Fasdf-vm.com\u002F) and [mise](https:\u002F\u002Fmise.jdx.dev\u002F) are tool version managers,\nmostly aimed towards project-specific tool versioning. However both support managing tools\nglobally in the user-space as well:\n\n\u003Cdetails>\u003Csummary>mise\u003C\u002Fsummary>\n\n[Install mise](https:\u002F\u002Fmise.jdx.dev\u002Fgetting-started.html), then run:\n\n```bash\nmise plugins install neovim\nmise use neovim@stable\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\u003Csummary>asdf\u003C\u002Fsummary>\n\n[Install asdf](https:\u002F\u002Fasdf-vm.com\u002Fguide\u002Fgetting-started.html), then run:\n\n```bash\nasdf plugin add neovim\nasdf install neovim stable\nasdf set neovim stable --home\nasdf reshim neovim\n```\n\n\u003C\u002Fdetails>\n\n\u003C\u002Fdetails>\n","kickstart.nvim 是一个用于个人 Neovim 配置的启动点。该项目提供了一个小巧且单文件形式的基础配置，完全文档化，易于理解和扩展。它并不作为一个完整的 Neovim 发行版，而是为用户提供了一个简洁的起点，以便在此基础上构建自己的个性化设置。适合那些希望从头开始定制 Neovim 但又不想面对空白配置文件挑战的开发者使用。项目支持最新的稳定版和每日构建版 Neovim，并依赖于一些基本工具如 git、make 和特定语言环境等。通过简单的安装步骤，用户可以快速搭建起功能齐全的开发环境。",2,"2026-06-11 03:32:54","high_star"]